Transmitting/receiving system and method for processing a broadcast signal

ABSTRACT

A method and broadcast terminal for receiving an emergency alert message in a sleep mode, are discussed. In one embodiment, the method includes monitoring fast information channel (FIC) wake-up indicator in an FIC segment to determine if the broadcast terminal should be switched to an active mode to receive the emergency alert message; getting an FIC-Chunk payload responsive to the FIC wake-up indicator in the FIC segment, the FIC-Chunk payload including an emergency alert data package indicator; receiving an alert data indicated by a data package identification included in the FIC-Chunk payload, the emergency alert data package indicator indicating an emergency alert table describing the emergency alert message is carried in the data; and parsing the emergency alert message based on the emergency alert table.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of co-pending U.S. patent application Ser. No. 14/119,823 filed on Nov. 22, 2013, which is the National Phase of PCT/KR2012/004167 filed on May 25, 2012, which claims the benefit of U.S. Provisional Application Nos. 61/489,683 filed on May 25, 2011, 61/493,964 filed Jun. 6, 2011, and 61/505,512 filed Jul. 7, 2011, the entire contents of all of the above applications are hereby incorporated by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a digital broadcasting system for transmitting and receiving digital broadcast signal, and more particularly, to a transmitting system for processing and transmitting digital broadcast signal, and a receiving system for receiving and processing digital broadcast signal and, a method of processing digital broadcast signal in the transmitting system and the receiving system.

2. Discussion of the Related Art

The Vestigial Sideband (VSB) transmission mode, which is adopted as the standard for digital broadcasting in North America and the Republic of Korea, is a system using a single carrier method. Therefore, the receiving performance of the digital broadcast receiving system may be deteriorated in a poor channel environment. Particularly, since resistance to changes in channels and noise is more highly required when using portable and/or mobile broadcast receivers, the receiving performance may be even more deteriorated when transmitting mobile service data by the VSB transmission mode.

SUMMARY OF THE INVENTION

An object of the present invention is to provide a transmitting system and a receiving system and a method of processing broadcast signal that are highly resistant to channel changes and noise.

Another object of the present invention is to provide a transmitting system and a receiving system and a method of processing broadcast signal that can enhance the receiving performance of the receiving system by performing additional encoding on mobile service data and by transmitting the processed data to the receiving system.

A further object of the present invention is to provide a transmitting system and a receiving system and a method of processing broadcast signal that can also enhance the receiving performance of the receiving system by inserting known data already known in accordance with a pre-agreement between the receiving system and the transmitting system in a predetermined region within a data region.

Yet another object of the present invention is to provide a transmitting system, a receiving system, and a method of processing a broadcast signal that may allow the transmitting system to signal and transmit information identifying an enhancement service, and that may then allow the receiving system to use the transmitted information so as to support to the enhancement service.

Another object of the present invention is to provide a transmitting system and a receiving system and a method of processing broadcast signals that allow the receiving system capable of receiving mobile broadcasts to provide a disaster alert service by transmitting an emergency alert message using a mobile broadcast network.

Another object of the present invention is to provide a signaling method and transmission/reception method for signaling information that allow the receiving system capable of receiving mobile broadcast to provide the disaster alert service.

Another object of the present invention is to provide a transmitting system and a receiving system and a method of processing broadcast signals which can efficiently provide a disaster alert service by providing additional information associated with the emergency alert message.

The object of the present invention can be achieved by providing a method for processing a broadcast signal in a transmitting system including the steps of performing Reed Solomon-Cyclic Redundancy Check (RS-CRC) encoding on mobile service data containing an emergency alert message and generating an RS frame belonging to an ensemble, dividing the RS frame into a plurality of RS frame portions, mapping the RS frame portions into respective data groups and inserting one fast information channel (FIC) segment and a plurality of known data sequences into each of the data groups, performing trellis encoding on data of the data groups, and transmitting the broadcast signal including the trellis-encoded data.

An FIC chunk is configured with an FIC chunk header and FIC chunk payload, signals biding information between the ensemble and a mobile service included in the ensemble, and is divided into a plurality of FIC segment payloads. The FIC segment is configured with an FIC segment header and one of the plurality of FIC segment payloads.

The FIC segment header includes wake-up indication information for compulsorily switching a broadcast receiver to an active mode according to a degree of severity of the emergency alert message.

The emergency alert message may be transmitted in a Common Alerting Protocol (CAP) form or a syntax form.

The ensemble may include at least one of a service map table (SMT) and an emergency alert table (EAT). Each of the SMT and the EAT comprises an ensemble identifier to identify the ensemble. Identifying information for identifying whether the emergency alert message is in the CAP form or in the syntax form may be signaled to at least one of the SMT and the EAT.

IP datagrams including the SMT and IP datagrams including the EAT may be transmitted over a service signaling channel. All the IP datagrams transmitted over the service signaling channel may have the same well-known IP address and the same well-known UDP port number.

The FIC chunk payload may include the ensemble identifier to identify the ensemble and indication information to indicate whether the EAT is transmitted over a service signaling channel included in the ensemble.

The method may further include the step of including disaster-related additional information associated with the emergency alert message in at least one file and transmitting the at least file including the disaster-related additional information in non-real time (NRT).

In another aspect of the present invention, provided herein is a transmitting system including a first encoder configured to perform Reed Solomon-Cyclic Redundancy Check (RS-CRC) encoding on mobile service data containing an emergency alert message and generate an RS frame belonging to an ensemble, a divider configured to divide the RS frame into a plurality of RS frame portions, a group formatter configured to map the RS frame portions into respective data groups and insert one fast information channel (FIC) segment and a plurality of known data sequences into each of the data groups, a second encoder configured to perform trellis encoding on data of the data groups, and a transmitting unit configured to transmit a broadcast signal including the trellis-encoded data.

An FIC chunk is configured with an FIC chunk header and FIC chunk payload, signals biding information between the ensemble and a mobile service included in the ensemble, and is divided into a plurality of FIC segment payloads. The FIC segment may be configured with an FIC segment header and one of the plurality of FIC segment payloads. The FIC segment header may include wake-up indication information for compulsorily switching a broadcast receiver to an active mode according to a degree of severity of the emergency alert message.

Other objects, features and advantages of the invention will be apparent from a detailed description of embodiments with reference to the accompanying drawings.

As described above, the transmitting system and the receiving system and the broadcast signal processing method of the same according to the present invention have the following advantages. When transmitting mobile service data through a channel, the present invention may be robust against errors and backward compatible with the conventional digital broadcast receiving system.

Moreover, the present invention may also receive the mobile service data without any error even in channels having severe ghost effect and noise.

Furthermore, by inserting known data in a particular position (or place) within a data region and transmitting the processed data, the receiving performance of the receiving system may be enhanced even in a channel environment that is liable to frequent changes.

In addition, by transmitting an emergency alert message using a mobile broadcast network in a mobile broadcast transmitter and, receiving and processing it by a mobile broadcast receiver, the broadcast receiver capable of receiving mobile broadcasts can provide a disaster alert service to a viewer.

Also, by transmitting and receiving additional information associated with the emergency alert message in non-real time and then by servicing to viewers, the disaster alert service can be serviced efficiently through mobile broadcast.

Finally, the present invention is even more effective when applied to mobile and portable receivers, which are also liable to a frequent change in channel and which require protection (or resistance) against intense noise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a structure of a M/H frame for transmitting and receiving mobile service data according to the present invention;

FIG. 2 illustrates an exemplary structure of a VSB frame;

FIG. 3 illustrates a mapping example of the positions to which the first 4 slots of a sub-frame are assigned with respect to a VSB frame in a space region;

FIG. 4 illustrates a mapping example of the positions to which the first 4 slots of a sub-frame are assigned with respect to a VSB frame in a time region;

FIG. 5 illustrates an alignment of data after being data interleaved and identified;

FIG. 6 illustrates an enlarged portion of the data group shown in FIG. 5 for a better understanding of the present invention;

FIG. 7 illustrates an alignment of data before being data interleaved and identified;

FIG. 8 illustrates an enlarged portion of the data group shown in FIG. 7 for a better understanding of the present invention;

FIG. 9 illustrates an exemplary assignment order of data groups being assigned to one of 5 sub-frames according to the present invention;

FIG. 10 illustrates an example of assigning a single parade to an M/H frame according to the present invention;

FIG. 11 illustrates an example of RS frame payload according to the present invention;

FIG. 12 is a diagram illustrating a structure of an M/H header within an M/H service data packet according to the present invention;

FIG. 13( a) and FIG. 13( b) are diagrams illustrating another example of RS frame payload according to the present invention; and

FIG. 14 illustrates a block diagram showing an embodiment of a transmitter according to the present invention;

FIG. 15 illustrates a block diagram showing an example of a pre-processor according to the present invention;

FIG. 16 illustrates a conceptual block diagram of the M/H frame encoder according to the present invention;

FIG. 17 illustrates a detailed block diagram of an RS frame encoder according to the present invention;

FIG. 18( a) and FIG. 18( b) illustrate a process of one or two RS frame being divided into several portions, based upon an RS frame mode value, and a process of each portion being assigned to a corresponding region within the respective data group;

FIG. 19( a) to FIG. 19( c) illustrate error correction encoding and error detection encoding processes according to an embodiment of the present invention;

FIG. 20( a) and FIG. 20( b) illustrate an example which a parade configures of two RS frames

FIG. 21( a) and FIG. 21( b) illustrate an exemplary process of dividing an RS frame for configuring a data group according to the present invention;

FIG. 22 illustrates a block diagram of a block processor according to an embodiment of the present invention;

FIG. 23 illustrates a detailed block diagram of a convolution encoder of the block processor;

FIG. 24 illustrates a symbol interleaver of the block processor;

FIG. 25 illustrates a block diagram of a group formatter according to an embodiment of the present invention;

FIG. 26 illustrates a block diagram of a trellis encoder according to an embodiment of the present invention;

FIG. 27 illustrates an example of assignment of training sequences within a data group before trellis encoding according to the present invention;

FIG. 28 illustrates an example of assignment of training sequences within a data group after trellis encoding according to the present invention;

FIG. 29 illustrates an example of assigning signaling information area according to an embodiment of the present invention;

FIG. 30 illustrates a detailed block diagram of a signaling encoder according to the present invention;

FIG. 31 illustrates an example of a syntax structure of TPC data according to the present invention;

FIG. 32 illustrates an example of a transmission scenario of the TPC data and the FIC data level according to the present invention;

FIG. 33 illustrates a syntax structure of an FIC chunk according to an embodiment of the present invention;

FIG. 34 illustrates a syntax structure of an FIC chunk header according to an embodiment of the present invention;

FIG. 35 illustrates a syntax structure of an FIC chunk payload according to an embodiment of the present invention;

FIG. 36 illustrates a syntax structure of an FIC segment header according to an embodiment of the present invention;

FIG. 37 illustrates a syntax structure of a service map table (SMT) according to an embodiment of the present invention;

FIG. 38 illustrates a bitstream syntax structure of component_descriptor( ) according to an embodiment of the present invention;

FIG. 39 illustrates a syntax structure of an FIC segment header according to an embodiment of the present invention;

FIG. 40 illustrates a syntax structure of an FIC segment header according to another embodiment of the present invention;

FIG. 41 illustrates a table showing meaning of values of a wake-up indicator field according to an embodiment of the present invention;

FIG. 42 illustrates a syntax structure of an FIC chunk payload according to another embodiment of the present invention;

FIG. 43 illustrates a syntax structure of an EAS message descriptor according to an embodiment of the present invention;

FIG. 44 illustrates a syntax structure of an EAS message descriptor according to another embodiment of the present invention;

FIG. 45 illustrates an example of signaling an EAS message descriptor to ensemble level according to an embodiment of the present invention;

FIG. 46 illustrates an example of signaling an EAS message descriptor to service level according to an embodiment of the present invention;

FIG. 47 illustrates an example of displaying an emergency alert message on a portion of screen according to an embodiment of the present invention;

FIG. 48 illustrates an example of displaying additional information related to an emergency alert message on another portion of screen according to an embodiment of the present invention;

FIG. 49 illustrates a syntax structure of capabilities descriptor according to the present invention;

FIG. 50 illustrates a syntax structure of NRT service descriptor according to the present invention;

FIG. 51 illustrates a table showing meaning of values of a consumption model field according to an embodiment of the present invention;

FIG. 52 illustrates a flow chart for receiving and displaying disaster information and disaster related-additional information by a broadcast receiver according to an embodiment of the present invention;

FIG. 53 illustrates a flow chart for receiving and displaying disaster information and disaster related-additional information by a broadcast receiver according to another embodiment of the present invention;

FIG. 54 illustrates an example of encapsulating an emergency alert message to IP datagram according to the present invention;

FIG. 55 illustrates an example of a syntax structure of emergency alert system descriptor capable of transmitting in a payload of IP datagram of FIG. 54;

FIG. 56 illustrates a table showing meaning of values of a service category field of SMT according to an embodiment of the present invention;

FIG. 57 illustrates an example of a bitstream syntax structure of component_data( ) providing signaling information for emergency alert message according to an embodiment of the present invention;

FIG. 58 illustrates an example of a bitstream syntax structure of EAT section according to an embodiment of the present invention;

FIG. 59 illustrates a flow chart for receiving and displaying disaster information and disaster related-additional information by a broadcast receiver according to another embodiment of the present invention; and

FIG. 60 illustrates a block diagram of a receiving system according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

Definition of Terms Used in the Present Invention

In addition, although the terms used in the present invention are selected from generally known and used terms, some of the terms mentioned in the description of the present invention have been selected by the applicant at his or her discretion, the detailed meanings of which are described in relevant parts of the description herein. Furthermore, it is required that the present invention is understood, not simply by the actual terms used but by the meaning of each term lying within.

Among the terms used in the description of the present invention, main service data correspond to data that can be received by a fixed receiving system and may include audio/video (A/V) data. More specifically, the main service data may include A/V data of high definition (HD) or standard definition (SD) levels and may also include diverse data types required for data broadcasting. Also, the known data correspond to data pre-known in accordance with a pre-arranged agreement between the receiving system and the transmitting system.

Additionally, among the terms used in the present invention, “M/H (or MH)” corresponds to the initials of “mobile” and “handheld” and represents the opposite concept of a fixed-type system. Furthermore, the M/H service data may include at least one of mobile service data and handheld service data, and will also be referred to as “mobile service data” for simplicity. Herein, the mobile service data not only correspond to M/H service data but may also include any type of service data with mobile or portable characteristics. Therefore, the mobile service data according to the present invention are not limited only to the M/H service data.

The above-described mobile service data may correspond to data having information, such as program execution files, stock information, and so on, and may also correspond to A/V data. Most particularly, the mobile service data may correspond to A/V data having lower resolution and lower data rate as compared to the main service data. For example, if an A/V codec that is used for a conventional main service corresponds to a MPEG-2 codec, a MPEG-4 advanced video coding (AVC) or scalable video coding (SVC) having better image compression efficiency may be used as the A/V codec for the mobile service. Furthermore, any type of data may be transmitted as the mobile service data. For example, transport protocol expert group (TPEG) data for broadcasting real-time transportation information may be transmitted as the main service data.

Also, a data service using the mobile service data may include weather forecast services, traffic information services, stock information services, viewer participation quiz programs, real-time polls and surveys, interactive education broadcast programs, gaming services, services providing information on synopsis, character, background music, and filming sites of soap operas or series, services providing information on past match scores and player profiles and achievements, and services providing information on product information and programs classified by service, medium, time, and theme enabling purchase orders to be processed. Herein, the present invention is not limited only to the services mentioned above.

In the present invention, the transmitting system provides backward compatibility in the main service data so as to be received by the conventional receiving system. Herein, the main service data and the mobile service data are multiplexed to the same physical channel and then transmitted.

Furthermore, the transmitting system according to the present invention performs additional encoding on the mobile service data and inserts the data already known by the receiving system and transmitting system (e.g., known data), thereby transmitting the processed data.

Therefore, when using the transmitting system according to the present invention, the receiving system may receive the mobile service data during a mobile state and may also receive the mobile service data with stability despite various distortion and noise occurring within the channel.

M/H Frame Structure

In the embodiment of the present invention, the mobile service data are first multiplexed with main service data in M/H frame units and, then, modulated in a VSB mode and transmitted to the receiving system.

At this point, one M/H frame configures of K1 number of sub-frames, wherein one sub-frame includes K2 number of slots. Also, each slot may be configured of K3 number of data packets. In the embodiment of the present invention, K1 will be set to 5, K2 will be set to 16, and K3 will be set to 156 (i.e., K1=5, K2=16, and K3=156). The values for K1, K2, and K3 presented in this embodiment either correspond to values according to a preferred embodiment or are merely exemplary. Therefore, the above-mentioned values will not limit the scope of the present invention.

FIG. 1 illustrates a structure of an M/H frame for transmitting and receiving mobile service data according to the present invention. In the example shown in FIG. 1, one M/H frame consists of 5 sub-frames, wherein each sub-frame includes 16 slots. In this case, the M/H frame according to the present invention includes 5 sub-frames and 80 slots.

Also, in a packet level, one slot is configured of 156 data packets (i.e., transport stream packets), and in a symbol level, one slot is configured of 156 data segments. Herein, the size of one slot corresponds to one half (½) of a VSB field. More specifically, since one 207-byte data packet has the same amount of data as a data segment, a data packet prior to being interleaved may also be used as a data segment.

At this point, two VSB fields are grouped to form a VSB frame.

FIG. 2 illustrates an exemplary structure of a VSB frame, wherein one VSB frame consists of 2 VSB fields (i.e., an odd field and an even field). Herein, each VSB field includes a field synchronization segment and 312 data segments.

The slot corresponds to a basic time period for multiplexing the mobile service data and the main service data. Herein, one slot may either include the mobile service data or be configured only of the main service data.

If one M/H frame is transmitted during one slot, the first 118 data packets within the slot correspond to a data group. And, the remaining 38 data packets become the main service data packets. In another example, when no data group exists in a slot, the corresponding slot is configured of 156 main service data packets.

Meanwhile, when the slots are assigned to a VSB frame, an offset exists for each assigned position.

FIG. 3 illustrates a mapping example of the positions to which the first 4 slots of a sub-frame are assigned with respect to a VSB frame in a space region. And, FIG. 4 illustrates a mapping example of the positions to which the first 4 slots of a sub-frame are assigned with respect to a VSB frame in a time region.

Referring to FIG. 3 and FIG. 4, a 38^(th) data packet (TS packet #37) of a 1^(st) slot (Slot #0) is mapped to the 1^(st) data packet of an odd VSB field. A 38^(th) data packet (TS packet #37) of a 2^(nd) slot (Slot #1) is mapped to the 157^(th) data packet of an odd VSB field. Also, a 38^(th) data packet (TS packet #37) of a 3^(rd) slot (Slot #2) is mapped to the 1^(st) data packet of an even VSB field. And, a 38^(th) data packet (TS packet #37) of a 4^(th) slot (Slot #3) is mapped to the 157^(th) data packet of an even VSB field. Similarly, the remaining 12 slots within the corresponding sub-frame are mapped in the subsequent VSB frames using the same method.

Meanwhile, one data group may be divided into at least one or more hierarchical regions. And, depending upon the characteristics of each hierarchical region, the type of mobile service data being inserted in each region may vary. For example, the data group within each region may be divided (or categorized) based upon the receiving performance.

In an example given in the present invention, a data group is divided into regions A, B, C, and D in a data configuration after data interleaving.

FIG. 5 illustrates an alignment of data after being data interleaved and identified. FIG. 6 illustrates an enlarged portion of the data group shown in FIG. 5 for a better understanding of the present invention. FIG. 7 illustrates an alignment of data before being data interleaved and identified. And, FIG. 8 illustrates an enlarged portion of the data group shown in FIG. 7 for a better understanding of the present invention. More specifically, a data structure identical to that shown in FIG. 5 is transmitted to a receiving system. In other words, one data packet is data-interleaved so as to be scattered to a plurality of data segments, thereby being transmitted to the receiving system. FIG. 5 illustrates an example of one data group being scattered to 170 data segments. At this point, since one 207-byte packet has the same amount of data as one data segment, the packet that is not yet processed with data-interleaving may be used as the data segment.

FIG. 5 shows an example of dividing a data group prior to being data-interleaved into 10 M/H blocks (i.e., M/H block 1 (B1) to M/H block 10 (B10)). In this example, each M/H block has the length of 16 segments. Referring to FIG. 5, only the RS parity data are allocated to a portion of 5 segments before the M/H block 1 (B1) and 5 segments behind the M/H block 10 (B10). The RS parity data are excluded in regions A to D of the data group.

More specifically, when it is assumed that one data group is divided into regions A, B, C, and D, each M/H block may be included in any one of region A to region D depending upon the characteristic of each M/H block within the data group. At this point, according to an embodiment of the present invention, each M/H block may be included in any one of region A to region D based upon an interference level of main service data.

Herein, the data group is divided into a plurality of regions to be used for different purposes. More specifically, a region of the main service data having no interference or a very low interference level may be considered to have a more resistant (or stronger) receiving performance as compared to regions having higher interference levels. Additionally, when using a system inserting and transmitting known data in the data group, wherein the known data are known based upon an agreement between the transmitting system and the receiving system, and when consecutively long known data are to be periodically inserted in the mobile service data, the known data having a predetermined length may be periodically inserted in the region having no interference from the main service data (i.e., a region wherein the main service data are not mixed). However, due to interference from the main service data, it is difficult to periodically insert known data and also to insert consecutively long known data to a region having interference from the main service data.

Referring to FIG. 5, M/H block 4 (B4) to M/H block 7 (B7) correspond to regions without interference of the main service data. M/H block 4 (B4) to M/H block 7 (B7) within the data group shown in FIG. 5 correspond to a region where no interference from the main service data occurs. In this example, a long known data sequence is inserted at both the beginning and end of each M/H block. In the description of the present invention, the region including M/H block 4 (B4) to M/H block 7 (B7) will be referred to as “region A (=B4+B5+B6+B7)”. As described above, when the data group includes region A having a long known data sequence inserted at both the beginning and end of each M/H block, the receiving system is capable of performing equalization by using the channel information that can be obtained from the known data. Therefore, the strongest equalizing performance may be yielded (or obtained) from one of region A to region D.

In the example of the data group shown in FIG. 5, MM/H block 3 (B3) and M/H block 8 (B8) correspond to a region having little interference from the main service data. Herein, a long known data sequence is inserted in only one side of each M/H block B3 and B8. More specifically, due to the interference from the main service data, a long known data sequence is inserted at the end of M/H block 3 (B3), and another long known data sequence is inserted at the beginning of M/H block 8 (B8). In the present invention, the region including M/H block 3 (B3) and M/H block 8 (B8) will be referred to as “region B(=B3+B8)”. As described above, when the data group includes region B having a long known data sequence inserted at only one side (beginning or end) of each M/H block, the receiving system is capable of performing equalization by using the channel information that can be obtained from the known data. Therefore, a stronger equalizing performance as compared to region C/D may be yielded (or obtained).

Referring to FIG. 5, M/H block 2 (B32) and M/H block 9 (B9) correspond to a region having more interference from the main service data as compared to region B. A long known data sequence cannot be inserted in any side of M/H block 2 (B2) and M/H block 9 (B9). Herein, the region including M/H block 2 (B2) and M/H block 9 (B9) will be referred to as “region C(=B2+B9)”. Finally, in the example shown in FIG. 5, M/H block 1 (B1) and M/H block 10 (B10) correspond to a region having more interference from the main service data as compared to region C. Similarly, a long known data sequence cannot be inserted in any side of M/H block 1 (B1) and M/H block 10 (B10).

Herein, the region including M/H block 1 (B1) and M/H block 10 (B10) will be referred to as “region D (=B1+B10)”. Since region C/D is spaced further apart from the known data sequence, when the channel environment undergoes frequent and abrupt changes, the receiving performance of region C/D may be deteriorated.

FIG. 7 illustrates a data structure prior to data interleaving. More specifically, FIG. 7 illustrates an example of 118 data packets being allocated to a data group. FIG. 7 shows an example of a data group consisting of 118 data packets, wherein, based upon a reference packet (e.g., a 1^(st) packet (or data segment) or 157^(th) packet (or data segment) after a field synchronization signal), when allocating data packets to a VSB frame, 37 packets are included before the reference packet and 81 packets (including the reference packet) are included afterwards.

In other words, with reference to FIG. 5, a field synchronization signal is placed (or assigned) between M/H block 2 (B2) and M/H block 3 (B3). Accordingly, this indicates that the slot has an off-set of 37 data packets with respect to the corresponding VSB field.

The size of the data groups, number of hierarchical regions within the data group, the size of each region, the number of M/H blocks included in each region, the size of each M/H block, and so on described above are merely exemplary. Therefore, the present invention will not be limited to the examples described above.

FIG. 9 illustrates an exemplary assignment order of data groups being assigned to one of 5 sub-frames, wherein the 5 sub-frames configure an M/H frame. For example, the method of assigning data groups may be identically applied to all M/H frames or differently applied to each M/H frame. Furthermore, the method of assigning data groups may be identically applied to all sub-frames or differently applied to each sub-frame. At this point, when it is assumed that the data groups are assigned using the same method in all sub-frames of the corresponding M/H frame, the total number of data groups being assigned to an M/H frame is equal to a multiple of ‘5’.

According to the embodiment of the present invention, a plurality of consecutive data groups is assigned to be spaced as far apart from one another as possible within the M/H frame. Thus, the system can be capable of responding promptly and effectively to any burst error that may occur within a sub-frame.

For example, when it is assumed that 3 data groups are assigned to a sub-frame, the data groups are assigned to a 1^(st) slot (Slot #0), a 5^(th) slot (Slot #4), and a 9^(th) slot (Slot #8) in the sub-frame, respectively. FIG. 9 illustrates an example of assigning 16 data groups in one sub-frame using the above-described pattern (or rule). In other words, each data group is serially assigned to 16 slots corresponding to the following numbers: 0, 8, 4, 12, 1, 9, 5, 13, 2, 10, 6, 14, 3, 11, 7, and 15.

Equation 1 below shows the above-described rule (or pattern) for assigning data groups in a sub-frame.

j=(4i+0)mod 16  Equation 1

-   -   0=0 if i<4,     -   0=2 else if i<8,     -   Herein, 0=1 else if i<12,     -   0=3 else.

Herein, j indicates the slot number within a sub-frame. The value of j may range from 0 to 15 (i.e., 0≦j≦15). Also, value of i indicates the data group number. The value of i may range from 0 to 15 (i.e., 0≦i≦15).

In the present invention, a collection of data groups included in an M/H frame will be referred to as a “parade”. Based upon the RS frame mode, the parade transmits data of one or two RS frames.

The mobile service data within one RS frame may be assigned (or mapped) either to all of regions A/B/C/D within the corresponding data group, or to at least one of regions A/B/C/D. In the embodiment of the present invention, the mobile service data within one RS frame may be assigned (or mapped) either to all of regions A/B/C/D, or to at least one of regions A/B and regions C/D. If the mobile service data are assigned to the latter case (i.e., one of regions A/B and regions C/D), the RS frame being assigned to regions A/B and the RS frame being assigned to regions C/D within the corresponding data group are different from one another. In the description of the present invention, the RS frame being assigned to regions A/B within the corresponding data group will be referred to as a “primary RS frame”, and the RS frame being assigned to regions C/D within the corresponding data group will be referred to as a “secondary RS frame”, for simplicity. Also, the primary RS frame and the secondary RS frame form (or configure) one parade. More specifically, when the mobile service data within one RS frame are assigned either to all of regions A/B/C/D within the corresponding data group, one parade transmits one RS frame. In this case, also the RS frame will be referred to as a “primary RS frame”. Conversely, when the mobile service data within one RS frame are assigned either to at least one of regions A/B and regions C/D, one parade may transmit up to 2 RS frames.

More specifically, the RS frame mode indicates whether a parade transmits one RS frame, or whether the parade transmits two RS frames.

Table 1 below shows an example of the RS frame mode.

TABLE 1 RS frame mode (2 bits) Description 00 There is only one primary RS frame for all group regions 01 There are two separate RS frames. Primary RS frame for group regions A and B Secondary RS frame for group regions C and D 10 Reserved 11 Reserved

Table 1 illustrates an example of allocating 2 bits in order to indicate the RS frame mode. For example, referring to Table 1, when the RS frame mode value is equal to ‘00’, this indicates that one parade transmits one RS frame. And, when the RS frame mode value is equal to ‘01’, this indicates that one parade transmits two RS frames, i.e., the primary RS frame and the secondary RS frame. More specifically, when the RS frame mode value is equal to ‘01’, data of the primary RS frame for regions A/B are assigned and transmitted to regions A/B of the corresponding data group. Similarly, data of the secondary RS frame for regions C/D are assigned and transmitted to regions C/D of the corresponding data group.

As described in the assignment of data groups, the parades are also assigned to be spaced as far apart from one another as possible within the sub-frame. Thus, the system can be capable of responding promptly and effectively to any burst error that may occur within a sub-frame.

Furthermore, the method of assigning parades may be identically applied to all sub-frames or differently applied to each sub-frame. According to the embodiment of the present invention, the parades may be assigned differently for each M/H frame and identically for all sub-frames within an M/H frame. More specifically, the M/H frame structure may vary by M/H frame units. Thus, an ensemble rate may be adjusted on a more frequent and flexible basis.

FIG. 10 illustrates an example of multiple data groups of a single parade being assigned (or allocated) to an M/H frame.

More specifically, FIG. 10 illustrates an example of a plurality of data groups included in a single parade, wherein the number of data groups included in a sub-frame is equal to ‘3’, being allocated to an M/H frame. Referring to FIG. 10, 3 data groups are sequentially assigned to a sub-frame at a cycle period of 4 slots. Accordingly, when this process is equally performed in the 5 sub-frames included in the corresponding M/H frame, 15 data groups are assigned to a single M/H frame. Herein, the 15 data groups correspond to data groups included in a parade. Therefore, since one sub-frame is configured of 4 VSB frame, and since 3 data groups are included in a sub-frame, the data group of the corresponding parade is not assigned to one of the 4 VSB frames within a sub-frame.

For example, when it is assumed that one parade transmits one RS frame, and that a RS frame encoder located in a later block performs RS-encoding on a payload of the corresponding RS frame, thereby adding 24 bytes of parity data to the corresponding RS frame payload and transmitting the processed RS frame, the parity data occupy approximately 11.37% (=24/(187+24)×100) of the total code word length. Meanwhile, when one sub-frame includes 3 data groups, and when the data groups included in the parade are assigned, as shown in FIG. 10, a total of 15 data groups form an RS frame. Accordingly, even when an error occurs in an entire data group due to a burst noise within a channel, the percentile is merely 6.67% (=1/15×100). Therefore, the receiving system may correct all errors by performing an erasure RS decoding process. More specifically, when the erasure RS decoding is performed, a number of channel errors corresponding to the number of RS parity bytes may be corrected. By doing so, the receiving system may correct the error of at least one data group within one parade. Thus, the minimum burst noise length correctable by a RS frame is over 1 VSB frame.

Meanwhile, when data groups belonging to a parade are assigned as shown in FIG. 10, either main service data may be assigned between each data group, or data groups corresponding to different parades may be assigned between each data group. More specifically, data groups corresponding to multiple parades may be assigned to one M/H frame.

Basically, the method of assigning data groups corresponding to multiple parades is very similar to the method of assigning data groups corresponding to a single parade. In other words, data groups included in other parades that are to be assigned to an M/H frame are also respectively assigned according to a cycle period of 4 slots.

At this point, data groups of a different parade may be sequentially assigned to the respective slots in a circular method. Herein, the data groups are assigned to slots starting from the ones to which data groups of the previous parade have not yet been assigned.

For example, when it is assumed that data groups corresponding to a parade are assigned as shown in FIG. 10, data groups corresponding to the next parade may be assigned to a sub-frame starting either from the 12^(th) slot of a sub-frame. However, this is merely exemplary. In another example, the data groups of the next parade may also be sequentially assigned to a different slot within a sub-frame at a cycle period of 4 slots starting from the 3^(rd) slot.

As described above, data groups of multiple parades may be assigned to a single M/H frame, and, in each sub-frame, the data groups are serially allocated to a group space having 4 slots from left to right.

Therefore, a number of groups of one parade per sub-frame (NOG) may correspond to any one integer from ‘1’ to ‘8’. Herein, since one M/H frame includes 5 sub-frames, the total number of data groups within a parade that can be allocated to an M/H frame may correspond to any one multiple of ‘5’ ranging from ‘5’ to ‘40’.

As described above, an M/H frame is divided into 5 sub-frames. Data groups corresponding to a plurality of parades co-exist in each sub-frame. Herein, the data groups corresponding to each parade are grouped by M/H frame units, thereby configuring a single parade.

Meanwhile, an RS frame according to the present invention includes an RS frame payload, RS parity data added at bottom of each column of the RS frame payload, and CRC data added at left end of each row of the RS frame payload having the RS parity data.

The RS frame payload has the size of N (row)×187 (column), as shown in FIG. 11. Herein, N represents the length of a row (i.e., number of columns), and 187 corresponds to the length of a column (i.e., number of rows.

In the present invention, for convenience of description, each row of the N bytes will be referred to as M/H service data packet (or M/H TP packet).

Each M/H service data packet within the RS frame payload includes M/H header (or MH TP header) of 2 bytes, a stuffing region of k bytes, and M/H payload of N-2-k bytes as shown in FIG. 12. At this time, k has a value of 0 or a value greater than 0. The M/H payload includes IP datagrams of signaling table information and/or mobile service data according to an embodiment of the present invention. In this case, the M/H header of 2 bytes is only one example, and corresponding bytes can be varied depending on a designer. Accordingly, the present invention will not be limited to such example.

At this time, as the M/H service data packet includes M/H header, the M/H header may not reach N bytes.

In this case, stuffing bytes can be assigned to the remaining payload part of the corresponding M/H service data packet. For example, after program table information is assigned to one M/H service data packet, if the length of the M/H service data packet is N-20 bytes including the M/H header, the stuffing bytes can be assigned to the remaining 20 bytes. In this case, the value k becomes 20, and the M/H payload region within the corresponding M/H service data packet includes N-2-20 bytes.

The RS frame payload is generated by collecting signaling table information corresponding to one or more mobile services and/or IP datagram of the mobile service data. For example, signaling table information for two kinds of mobile services called news (for example, IP datagram for mobile service 1) and the stocks (for example, IP datagram for mobile service 2) and IP datagram of mobile service data can be included in one RS frame payload.

More specifically, in the transmitting system (e.g., mobile broadcast station), the mobile service data (e.g., A/V steaming) are packetized based upon a real time protocol (RTP) method. The RTP packet is then packetized once again based upon a user datagram protocol (UDP) method. Thereafter, the RTP/UDP packet is in turn packetized based upon an IP method, thereby being packetized into RTP/UDP/IP packet data. In the description of the present invention, the packetized RTP/UDP/IP packet data will be referred to as an IP datagram for simplicity.

Furthermore, service information for receiving mobile services may be provided in the form of a signaling table. And, a service signaling channel transmitting such signaling table is packetized based upon a UDP method. And, the packetized UDP data are then packetized based upon an IP method, thereby being packetized into UDP/IP data. In the description of the present invention, the packetized UDP/IP packet data will also be referred to as an IP datagram for simplicity. According to an embodiment of the present invention, the service signaling channel is encapsulated into an IP datagram having a well-known destination IP address and a well-known destination UDP port number.

More specifically, one RS frame payload includes an IP datagram of mobile service data for at least one or more mobile services. Furthermore, the RS frame payload includes an IP datagram of a service signaling channel for receiving the mobile service data.

According to the embodiment of the present invention, among a service map table (SMT), a guide access table (GAT), a cell information table (CIT), a service labeling table (SLT), and a rating region table (RRT), the present invention transmits at least one signaling table through the service signaling channel. Herein, the signaling tables presented in the embodiment of the present invention are merely examples for facilitating the understanding of the present invention. Therefore, the present invention is not limited only to the exemplary signaling tables that can be transmitted through the service signaling channel.

The SMT provides signaling information on ensemble levels. Also, each SMT provides IP access information for each mobile service belonging to the corresponding ensemble including each SMT. Furthermore, the SMT provides IP stream component level information required for the corresponding mobile service. The RRT transmits information on region and consultation organs for program ratings. More specifically, the RRT provides content advisory rating information. The GAT provides information on SG providers, which transmit the service guides. Also, the GAT provides service guide bootstrapping information required for accessing the SG. The CIT provides channel information of each cell, which corresponds to the frequency domain of a broadcast signal. Herein, a cell refers to a scope affected (or influenced) by a transmitter based upon a physical frequency in a multi-frequency network (MFN) environment (or condition). More specifically, the CIT provides information on a carrier wave frequency of an adjacent cell in the current transmitter (or transmitting system). Therefore, based upon the CIT information, a receiver (or receiving system) can travel from one transmitter's (or exciter's) coverage area to another. The SLT provides minimum required information for an exclusive usage of a channel scan process. More specifically, according to the embodiment of the present invention, other than the SMT, by using the SLT for the exclusive usage of the channel scan process, so as to configure a set of minimum information for the channel scan process, the channel scanning speed may be increased.

According to an embodiment of the present invention, each signaling table is divided into at least one section. Then, each section is encapsulated to a UDP/IP header, thereby being transmitted through the service signaling channel. In this case, the number of UDP/IP packets being transmitted through the service signaling channel may vary based upon the number of signaling tables being transmitted through the service signaling channel and the number of sections in each signaling table.

At this point, all UDP/IP packets transmitted through the service signaling channel have the same number of well-known target IP addresses and well-known target UDP port numbers. For example, when it is assumed that the SMT, RRT, and GAT are transmitted through the service signaling channel, the target IP address and target UDP port number of all UDP/IP packets transmitting the SMT, RRT, and GAT are identical to one another. Furthermore, the target IP address and the target UDP port number respectively correspond to well-known values, i.e., values pre-known by the receiving system based upon an agreement between the receiving system and the transmitting system.

Therefore, the identification of each signaling table included in the service signaling data is performed by a table identifier. The table identifier may correspond to a table_id field existing in the corresponding signaling table or in the header of the corresponding signaling table section. And, when required, identification may be performed by further referring to a table_id_extension field.

FIG. 12 is a diagram illustrating examples of fields allocated to the M/H header region within the M/H service data packet according to the present invention. Examples of the fields include type_indicator field, error_indicator field, stuff_indicator field, and pointer field.

The type_indicator field can allocate 3 bits, for example, and represents a type of data allocated to payload within the corresponding M/H service data packet. In other words, the type_indicator field indicates whether data of the payload is IP datagram or program table information. At this time, each data type constitutes one logical channel. In the logical channel which transmits the IP datagram, several mobile services are multiplexed and then transmitted. Each mobile service undergoes demultiplexing in the IP layer.

The error_indicator field can allocate 1 bit, for example, and represents whether the corresponding M/H service data packet has an error. For example, if the error_indicator field has a value of 0, it means that there is no error in the corresponding M/H service data packet. If the error_indicator field has a value of 1, it means that there may be an error in the corresponding M/H service data packet. According to an embodiment of the present invention, a value of zero are indicated and transmitted on all error_indicator fields within the RS frame.

The stuff_indicator field can allocate 1 bit, for example, and represents whether stuffing byte exists in payload of the corresponding M/H service data packet. For example, if the stuff_indicator field has a value of 0, it means that there is no stuffing byte in the corresponding M/H service data packet. If the stuff_indicator field has a value of 1, it means that stuffing byte exists in the corresponding M/H service data packet.

The pointer field can allocate 11 bits, for example, and represents position information where new data (i.e., new signaling information or new IP datagram) starts in the corresponding M/H service data packet.

For example, if IP datagram for mobile service 1 and IP datagram for mobile service 2 are allocated to the first M/H service data packet within the RS frame payload as illustrated in FIG. 11, the pointer field value represents the start position of the IP datagram for mobile service 2 within the M/H service data packet.

Also, if there is no new data in the corresponding M/H service data packet, the corresponding field value is expressed as a maximum value exemplarily. According to the embodiment of the present invention, since 11 bits are allocated to the pointer field, if 2047 is expressed as the pointer field value, it means that there is no new data in the packet. The point where the pointer field value is 0 can be varied depending on the type_indicator field value and the stuff_indicator field value.

It is to be understood that the order, the position, and the meaning of the fields allocated to the header within the M/H service data packet illustrated in FIG. 12 are exemplarily illustrated for understanding of the present invention. Since the order, the position and the meaning of the fields allocated to the header within the M/H service data packet and the number of additionally allocated fields can easily be modified by those skilled in the art, the present invention will not be limited to the above example.

FIG. 13( a) and FIG. 13( b) illustrate another examples of RS frame payload according to the present invention. FIG. 13( a) illustrates an example of primary RS frame payload to be allocated to regions A/B within the data group, and FIG. 13( b) illustrates an example of secondary RS frame payload to be allocated to regions C/D within the data group.

In FIG. 13( a) and FIG. 13( b), a column length (i.e., the number of rows) of the RS frame payload to be allocated to the regions A/B and a column length (i.e., the number of rows) of the RS frame payload to be allocated to the regions C/D are 187 equally. However, row lengths (i.e, the number of columns) may be different from each other.

According to the embodiment of the present invention, when the row length of the primary RS frame payload to be allocated to the regions A/B within the data group is N1 bytes and the row length of the secondary RS frame payload to be allocated to the regions C/D within the data group is N2 bytes, a condition of N1>N2 is satisfied.

In this case, N1 and N2 can be varied depending on the transmission parameter or a region of the data group, to which the corresponding RS frame payload will be transmitted.

For convenience of the description, each row of the N1 and N2 bytes will be referred to as the M/H service data packet. In the present invention, the primary RS frame payload for the regions A/B within the data group and the secondary RS frame payload for the regions C/D within the data group can include at least one of IP datagrams of signaling table information and mobile service data. Also, one RS frame payload can include IP datagram corresponding to one or more mobile services.

Corresponding parts of FIG. 1 can be applied to the other parts, which are not described in FIG. 13( a) and FIG. 13( b).

Meanwhile, the value of N, which corresponds to the number of columns within an RS frame payload, can be decided according to Equation 2.

$\begin{matrix} {N = {\left\lfloor \frac{5 \times {NoG} \times {PL}}{187 \div P} \right\rfloor - 2}} & {{Equation}\mspace{14mu} 2} \end{matrix}$

Herein, NoG indicates the number of data groups assigned to a sub-frame. PL represents the number of SCCC payload data bytes assigned to a data group. And, P signifies the number of RS parity data bytes added to each column of the RS frame payload. Finally, └X┘ is the greatest integer that is equal to or smaller than X.

More specifically, in Equation 2, PL corresponds to the length of an RS frame portion. The value of PL is equivalent to the number of SCCC payload data bytes that are assigned to the corresponding data group. Herein, the value of PL may vary depending upon the RS frame mode, SCCC block mode, and SCCC outer code mode. Table 2 to Table 5 below respectively show examples of PL values, which vary in accordance with the RS frame mode, SCCC block mode, and SCCC outer code mode. The SCCC block mode and the SCCC outer code mode will be described in detail in a later process.

TABLE 2 SCCC outer code mode for Region A for Region B for Region C for Region D PL 00 00 00 00 9624 00 00 00 01 9372 00 00 01 00 8886 00 00 01 01 8634 00 01 00 00 8403 00 01 00 01 8151 00 01 01 00 7665 00 01 01 01 7413 01 00 00 00 7023 01 00 00 01 6771 01 00 01 00 6285 01 00 01 01 6033 01 01 00 00 5802 01 01 00 01 5550 01 01 01 00 5064 01 01 01 01 4812 Others Reserved

Table 2 shows an example of the PL values for each data group within an RS frame, wherein each PL value varies depending upon the SCCC outer code mode, when the RS frame mode value is equal to ‘00’, and when the SCCC block mode value is equal to ‘00’.

For example, when it is assumed that each SCCC outer code mode value of regions A/B/C/D within the data group is equal to ‘00’ (i.e., the block processor 302 of a later block performs encoding at a coding rate of ½), the PL value within each data group of the corresponding RS frame may be equal to 9624 bytes. More specifically, 9624 bytes of mobile service data within one RS frame may be assigned to regions A/B/C/D of the corresponding data group.

TABLE 3 SCCC outer code mode PL 00 9624 01 4812 Others Reserved

Table 3 shows an example of the PL values for each data group within an RS frame, wherein each PL value varies depending upon the SCCC outer code mode, when the RS frame mode value is equal to ‘00’, and when the SCCC block mode value is equal to ‘01’.

TABLE 4 SCCC outer code mode For Region A for Region B PL 00 00 7644 00 01 6423 01 00 5043 01 01 3822 Others Reserved

Table 4 shows an example of the PL values for each data group within a primary RS frame, wherein each PL value varies depending upon the SCCC outer code mode, when the RS frame mode value is equal to ‘01’, and when the SCCC block mode value is equal to ‘00’. For example, when each SCCC outer code mode value of regions A/B is equal to ‘00’, 7644 bytes of mobile service data within a primary RS frame may be assigned to regions A/B of the corresponding data group.

TABLE 5 SCCC outer code mode For Region C for Region D PL 00 00 1980 00 01 1728 01 00 1242 01 01 990 Others Reserved

Table 5 shows an example of the PL values for each data group within a secondary RS frame, wherein each PL value varies depending upon the SCCC outer code mode, when the RS frame mode value is equal to ‘01’, and when the SCCC block mode value is equal to ‘00’. For example, when each SCCC outer code mode value of regions C/D is equal to ‘00’, 1980 bytes of mobile service data within a secondary RS frame may be assigned to regions C/D of the corresponding data group.

Meanwhile, a predetermined portion of each data group (i.e., 37 bytes/data group) is used for delivering (or sending) FIC information (i.e., one FIC segment), wherein the FIC information is separately encoded from the RS-encoding process on the mobile service data.

Also, the concept of an M/H ensemble is applied in the embodiment of the present invention, thereby defining a collection (or group) of services. Each M/H ensemble carries the same QoS and is coded with the same FEC code. Herein, the M/H ensemble is used as the same meaning of ensemble. Furthermore, each ensemble has a unique identifier (i.e., ensemble ID) and corresponds to consecutive RS frames.

A transmitting/receiving system according to an embodiment of the present invention operates (or manages) two data channels. One data channel is an RS frame data channel for transmitting contents and the other data channel is an FIC (Fast Information Channel) for service acquisition. The present invention is intended that mapping (binding) information between an ensemble and a mobile service is signaled using an FIC chunk and the FIC chunk is transmitted through the FIC by being segmented into an FIC segment unit, whereby the receiving system can perform fast service acquisition.

Transmitter

FIG. 14 illustrates a block diagram showing an example of the transmitter according to an embodiment of the present invention. Herein, the transmitter includes a packet jitter mitigator 220, a pre-processor 230, a packet multiplexer 240, a post-processor 250, a synchronization (sync) multiplexer 260, and a transmission unit 270.

At this point, main service data are inputted to the packet jitter mitigator 220 and mobile service data are inputted to the pre-processor 230 according to an embodiment of the present invention. Furthermore, main service data packets including main service data can be inputted to the packet jitter mitigator 220 and mobile service data packets including mobile service data can be inputted to the pre-processor 230 according to another embodiment of the present invention.

The pre-processor 230 performs an additional encoding process of the mobile service data inputted. The pre-processor 230 also performs a process of configuring a data group so that the data group may be positioned at a specific place in accordance with the purpose of the data, which are to be transmitted on a transmission frame. This is to enable the mobile service data to respond swiftly and strongly against noise and channel changes. FIG. 15 illustrates a block diagram showing the structure of a pre-processor 230 according to the present invention. Herein, the pre-processor 230 includes an M/H frame encoder 301, a block processor 302, a group formatter 303, a signaling encoder 304, and a packet formatter 305.

The M/H frame encoder 301, which is included in the pre-processor 230 having the above-described structure, data-randomizes the mobile service data inputted, thereby forming at least one RS frame belonging to an ensemble. The M/H frame encoder 301 may include at least one RS frame encoder. More specifically, RS frame encoders may be provided in parallel, wherein the number of RS frame encoders is equal to the number of parades within the M/H frame. As described above, the M/H frame is a basic time cycle period for transmitting at least one parade. Also, each parade consists of one or two RS frames.

FIG. 16 illustrates a conceptual block diagram of the M/H frame encoder 301 according to an embodiment of the present invention. The M/H frame encoder 301 includes an input demultiplexer (DEMUX) 309, M number of RS frame encoders 310 to 31M-1, and an output multiplexer (MUX) 320. Herein, M represent the number of parades included in one M/H frame.

The demultiplexer 309 output the inputted mobile service data packet to a corresponding RS frame encoder among M number of RS frame encoders in ensemble units.

According to an embodiment of the present invention, each RS frame encoder forms an RS frame payload using mobile service data inputted and performs at least one of an error correction encoding process and an error detection encoding process in RS frame payload units, thereby forming an RS frame. Also, each RS frame encoder divides the RS frame into a plurality of portions, in order to assign the error-correction-encoded RS frame data to a plurality of data groups. Based upon the RS frame mode of Table 1, data within one RS frame may be assigned either to all of regions A/B/C/D within multiple data groups, or to at least one of regions A/B and regions C/D within multiple data groups.

When the RS frame mode value is equal to ‘01’, i.e., when the data of the primary RS frame are assigned to regions A/B of the corresponding data group and data of the secondary RS frame are assigned to regions C/D of the corresponding data group, each RS frame encoder creates a primary RS frame and a secondary RS frame for each parade. Conversely, when the RS frame mode value is equal to ‘00’, when the data of the primary RS frame are assigned to all of regions A/B/C/D, each RS frame encoder creates a RS frame (i.e., a primary RS frame) for each parade.

Also, each RS frame encoder divides each RS frame into several portions. Each portion of the RS frame is equivalent to a data amount that can be transmitted by a data group. The output multiplexer (MUX) 320 multiplexes portions within M number of RS frame encoders 310 to 310M-1 are multiplexed and then outputted to the block processor 302.

For example, if one parade transmits two RS frames, portions of primary RS frames within M number of RS frame encoders 310 to 310M-1 are multiplexed and outputted. Thereafter, portions of secondary RS frames within M number of RS frame encoders 310 to 310M-1 are multiplexed and transmitted.

FIG. 17 illustrates a detailed block diagram of an RS frame encoder among a plurality of RS frame encoders within an M/H frame encoder.

One RS frame encoder may include a primary encoder 410 and a secondary encoder 420. Herein, the secondary encoder 420 may or may not operate based upon the RS frame mode. For example, when the RS frame mode value is equal to ‘00’, as shown in Table 1, the secondary encoder 420 does not operate.

The primary encoder 410 may include a data randomizer 411, a Reed-Solomon-cyclic redundancy check (RS-CRC) encoder (412), and a RS frame divider 413. And, the secondary encoder 420 may also include a data randomizer 421, a RS-CRC encoder (422), and a RS frame divider 423.

More specifically, the data randomizer 411 of the primary encoder 410 receives mobile service data belonging to a primary ensemble outputted from the output demultiplexer (DEMUX) 309. Then, after randomizing the received mobile service data, the data randomizer 411 outputs the randomized data to the RS-CRC encoder 412.

The RS-CRC encoder 412 performs FEC (Forward Error Correction) encoding on the randomized mobile service data using at least one of a Reed-Solomon (RS) code and a cyclic redundancy check (CRC) code and outputs to the RS frame divider 413.

The RS-CRC encoder 412 groups a plurality of mobile service data that is randomized and inputted, so as to form a RS frame payload. Then, the RS-CRC encoder 412 performs at least one of an error correction encoding process and an error detection encoding process in RS frame payload units, thereby forming an RS frame. Accordingly, robustness may be provided to the mobile service data, thereby scattering group error that may occur during changes in a frequency environment, thereby enabling the mobile service data to respond to the frequency environment, which is extremely vulnerable and liable to frequent changes.

Also, the RS-CRC encoder 412 groups a plurality of RS frame so as to create a super frame, thereby performing a row permutation process in super frame units. The row permutation process may also be referred to as a “row interleaving process”. Hereinafter, the process will be referred to as “row permutation” for simplicity. In the present invention, the row permutation process is optional.

More specifically, when the RS-CRC encoder 412 performs the process of permuting each row of the super frame in accordance with a pre-determined rule, the position of the rows within the super frame before and after the row permutation process is changed. If the row permutation process is performed by super frame units, and even though the section having a plurality of errors occurring therein becomes very long, and even though the number of errors included in the RS frame, which is to be decoded, exceeds the extent of being able to be corrected, the errors become dispersed within the entire super frame. Thus, the decoding ability is even more enhanced as compared to a single RS frame.

At this point, as an example of the present invention, RS-encoding is applied for the error correction encoding process, and a cyclic redundancy check (CRC) encoding is applied for the error detection process in the RS-CRC encoder 412. When performing the RS-encoding, parity data that are used for the error correction are generated. And, when performing the CRC encoding, CRC data that are used for the error detection are generated.

The CRC data generated by CRC encoding may be used for indicating whether or not the mobile service data have been damaged by the errors while being transmitted through the channel. In the present invention, a variety of error detection coding methods other than the CRC encoding method may be used, or the error correction coding method may be used to enhance the overall error correction ability of the receiving system.

FIG. 18( a) and FIG. 18( b) illustrate a process of one or two RS frame being divided into several portions, based upon an RS frame mode value, and a process of each portion being assigned to a corresponding region within the respective data group. According to an embodiment of the present invention, the data assignment within the data group is performed by the group formatter 303.

More specifically, FIG. 18( a) shows an example of the RS frame mode value being equal to ‘00’. Herein, only the primary encoder 410 of FIG. 17 operates, thereby forming one RS frame for one parade. Then, the RS frame is divided into several portions, and the data of each portion are assigned to regions A/B/C/D within the respective data group.

FIG. 18( b) shows an example of the RS frame mode value being equal to ‘01’. Herein, both the primary encoder 410 and the secondary encoder 420 of FIG. 17 operate, thereby forming two RS frames for one parade, i.e., one primary RS frame and one secondary RS frame. Then, the primary RS frame is divided into several portions, and the secondary RS frame is divided into several portions. At this point, the data of each portion of the primary RS frame are assigned to regions A/B within the respective data group. And, the data of each portion of the secondary RS frame are assigned to regions C/D within the respective data group.

Detailed Description of the RS Frame

FIG. 19( a) illustrates an example of an RS frame being generated from the RS-CRC encoder 412 according to the present invention.

When the RS frame payload is formed, as shown in FIG. 19( a), the RS-CRC encoder 412 performs a (Nc,Kc)−RS encoding process on each column, so as to generate Nc−Kc(=P) number of parity bytes. Then, the RS-CRC encoder 412 adds the newly generated P number of parity bytes after the very last byte of the corresponding column, thereby creating a column of (187+P) bytes.

Herein, as shown in FIG. 19( a), Kc is equal to 187 (i.e., Kc=187), and Nc is equal to 187+P (i.e., Nc=187+P).

Herein, the value of P may vary depending upon the RS code mode. Table 6 below shows an example of an RS code mode, as one of the RS encoding information.

TABLE 6 RS code mode RS code Number of Parity Bytes (P) 00 (211, 187) 24 01 (223, 187) 36 10 (235, 187) 48 11 Reserved Reserved

Table 6 shows an example of 2 bits being assigned in order to indicate the RS code mode. The RS code mode represents the number of parity bytes corresponding to the RS frame payload.

For example, when the RS code mode value is equal to ‘10’, (235,187)-RS-encoding is performed on the RS frame payload of FIG. 19( a), so as to generate 48 parity data bytes. Thereafter, the 48 parity bytes are added after the last data byte of the corresponding column, thereby creating a column of 235 data bytes.

When the RS frame mode value is equal to ‘00’ in Table 1 (i.e., when the RS frame mode indicates a single RS frame), only the RS code mode of the corresponding RS frame is indicated. However, when the RS frame mode value is equal to ‘01’ in Table 1 (i.e., when the RS frame mode indicates multiple RS frames), the RS code mode corresponding to a primary RS frame and a secondary RS frame. More specifically, it is preferable that the RS code mode is independently applied to the primary RS frame and the secondary RS frame.

When such RS encoding process is performed on all N number of columns, a size of N(row)×(187+P)(column) bytes may be generated, as shown in FIG. 19( b).

Each row of the RS frame payload is configured of N bytes. However, depending upon channel conditions between the transmitting system and the receiving system, error may be included in the RS frame payload. When errors occur as described above, CRC data (or CRC code or CRC checksum) may be used on each row unit in order to verify whether error exists in each row unit.

The RS-CRC encoder 412 may perform CRC encoding on the mobile service data being RS encoded so as to create (or generate) the CRC data. The CRC data being generated by CRC encoding may be used to indicate whether the mobile service data have been damaged while being transmitted through the channel.

The present invention may also use different error detection encoding methods other than the CRC encoding method. Alternatively, the present invention may use the error correction encoding method to enhance the overall error correction ability of the receiving system.

FIG. 19( c) illustrates an example of using a 2-byte (i.e., 16-bit) CRC checksum as the CRC data. Herein, a 2-byte CRC checksum is generated for N number of bytes of each row, thereby adding the 2-byte CRC checksum at the end of the N number of bytes. Thus, each row is expanded to (N+2) number of bytes.

Equation 3 below corresponds to an exemplary equation for generating a 2-byte CRC checksum for each row being configured of N number of bytes.

g(x)=x ¹⁶ +x ¹² +x ⁵÷1  Equation 3

The process of adding a 2-byte checksum in each row is only exemplary. Therefore, the present invention is not limited only to the example proposed in the description set forth herein.

As described above, when the process of RS encoding and CRC encoding are completed, the (N×187)-byte RS frame payload is converted into a (N+2)×(187+P)-byte RS frame.

Based upon an error correction scenario of a RS frame formed as described above, the data bytes within the RS frame are transmitted through a channel in a row direction. At this point, when a large number of errors occur during a limited period of transmission time, errors also occur in a row direction within the RS frame being processed with a decoding process in the receiving system. However, in the perspective of RS encoding performed in a column direction, the errors are shown as being scattered. Therefore, error correction may be performed more effectively. At this point, a method of increasing the number of parity data bytes (P) may be used in order to perform a more intense error correction process. However, using this method may lead to a decrease in transmission efficiency. Therefore, a mutually advantageous method is required. Furthermore, when performing the decoding process, an erasure decoding process may be used to enhance the error correction performance.

The above description of the present invention corresponds to the processes of forming (or creating) and encoding an RS frame, when a data group is divided into regions A/B/C/D, and when data of an RS frame are assigned to all of regions A/B/C/D within a plurality of data groups. More specifically, the above description corresponds to an embodiment of the present invention, wherein one RS frame is transmitted using one parade. In this embodiment, the secondary encoder 420 does not operate (or is not active).

Meanwhile, 2 RS frames are transmitting using one parade, the data of the primary RS frame may be assigned to regions A/B within the data groups and be transmitted, and the data of the secondary RS frame may be assigned to regions C/D within the data groups and be transmitted. At this point, the primary encoder 410 receives the mobile service data that are to be assigned to regions A/B within the data groups, forms the primary RS frame payload, and then performs RS-encoding and CRC-encoding on the primary RS frame payload, thereby forming the primary RS frame. Similarly, the secondary encoder 420 receives the mobile service data that are to be assigned to regions C/D within the data groups, forms the secondary RS frame payload, and then performs RS-encoding and CRC-encoding on the secondary RS frame payload thereby forming the secondary RS frame. More specifically, the primary RS frame and the secondary RS frame are generated independently.

FIG. 20 illustrates examples of receiving the mobile service data that are to be assigned to regions A/B within the data group, so as to form the primary RS frame payload, and receives the mobile service data that are to be assigned to regions C/D within the data group, so as to form the secondary RS frame payload, thereby performing error correction encoding and error detection encoding on each of the first and secondary RS frame payloads.

More specifically, FIG. 20( a) illustrates an example of the RS-CRC encoder 412 of the primary encoder 410 receiving mobile service data of the primary ensemble that are to be assigned to regions A/B within the corresponding data group, so as to create an RS frame payload having the size of N1(row)×187(column). Then, in this example, the primary encoder 410 performs RS-encoding on each column of the RS frame payload created as described above, thereby adding P1 number of parity data bytes in each column. Finally, the primary encoder 410 performs CRC-encoding on each row, thereby adding a 2-byte checksum in each row, thereby forming an primary RS frame.

FIG. 20( b) illustrates an example of the RS-CRC encoder 422 of the secondary encoder 420 receiving mobile service data of the secondary ensemble that are to be assigned to regions C/D within the corresponding data group, so as to create an RS frame payload having the size of N2(row)×187(column). Then, in this example, the secondary encoder 420 performs RS-encoding on each column of the RS frame payload created as described above, thereby adding P2 number of parity data bytes in each column. Finally, the secondary encoder 420 performs CRC-encoding on each row, thereby adding a 2-byte checksum in each row, thereby forming an secondary RS frame.

At this point, each of the RS-CRC encoders 412 and 422 performs RS frame configuration, error correction encoding, error detection encoding by referring to a transmission parameter, for example, at least one of M/H frame information, FIC information, RS frame information (including RS frame mode information), RS encoding information (including RS code mode information). SCCC information (including SCCC block mode information and SCCC outer code mode information). Furthermore, the transmission parameters should also be transmitted to the receiving system so that the receiving system can perform a normal decoding process. At this point, as an example of the present invention, the transmission parameter is transmitted through transmission parameter channel (TPC) to a receiving system. The TPC will be described in detail in a later.

The data of the primary RS frame, which is encoded by RS frame units by the RS-CRC encoder 412 of the primary encoder 410, are outputted to the RS frame divider 413. If the secondary encoder 420 also operates in the embodiment of the present invention, the data of the secondary RS frame, which is encoded by RS frame units by the RS-CRC encoder 422 of the secondary encoder 420, are outputted to the RS frame divider 423.

The RS frame divider 413 of the primary encoder 410 divides the primary RS frame into several portions, which are then outputted to the output multiplexer (MUX) 320. Each portion of the primary RS frame is equivalent to a data amount that can be transmitted by one data group. Similarly, the RS frame divider 423 of the secondary encoder 420 divides the secondary RS frame into several portions, which are then outputted to the output multiplexer (MUX) 320.

Hereinafter, the RS frame divider 413 of the primary RS encoder 410 will now be described in detail. Also, in order to simplify the description of the present invention, it is assumed that an RS frame payload having the size of N(row)×187(column), as shown in FIG. 19( a) to FIG. 19( c), that P number of parity data bytes are added to each column by RS-encoding the RS frame payload, and that a 2-byte checksum is added to each row by CRC-encoding the RS frame payload. As a result, an RS frame having the size of (N+2) (row)×187+P (column) is formed.

Accordingly, the RS frame divider 413 divides (or partitions) the RS frame having the size of (N+2) (row)×187+P (column) into several portions, each having the size of PL (wherein PL corresponds to the length of the RS frame portion).

At this point, as shown in Table 2 to Table 5, the value of PL may vary depending upon the RS frame mode, SCCC block mode, and SCCC outer coder mode. Also, the total number of data bytes of the RS-encoded and CRC-encoded RS frame is equal to or smaller than 5×NoG×PL. In this case, the RS frame is divided (or partitioned) into ((5×NoG)−1) number of portions each having the size of PL and one portion having a size equal to smaller than PL. More specifically, with the exception of the last portion of the RS frame, each of the remaining portions of the RS frame has an equal size of PL.

If the size of the last portion is smaller than PL, a stuffing byte (or dummy byte) may be inserted in order to fill (or replace) the lacking number of data bytes, thereby enabling the last portion of the RS frame to also be equal to PL.

Each portion of an RS frame corresponds to the amount of data that are to be SCCC-encoded and mapped into a single data group of a parade.

FIG. 21( a) and FIG. 21( b) respectively illustrate examples of adding S number of stuffing bytes, when an RS frame having the size of (N+2)(row)×(187+P)(column) is divided into 5×NoG number of portions, each having the size of PL.

More specifically, the RS-encoded and CRC-encoded RS frame, shown in FIG. 21( a), is divided into several portions, as shown in FIG. 21( b). The number of divided portions at the RS frame is equal to (5×NoG). Particularly, the first ((5×NoG)−1) number of portions each has the size of PL, and the last portion of the RS frame may be equal to or smaller than PL. If the size of the last portion is smaller than PL, a stuffing byte (or dummy byte) may be inserted in order to fill (or replace) the lacking number of data bytes, as shown in Equation 4 below, thereby enabling the last portion of the RS frame to also be equal to PL.

S=(5×NoG×PL)−((N÷2)×(187+P))  Equation 4

Herein, each portion including data having the size of PL passes through the output multiplexer 320 of the M/H frame encoder 301, which is then outputted to the block processor 302.

At this point, the mapping order of the RS frame portions to a parade of data groups in not identical with the group assignment order defined in Equation 1. When given the group positions of a parade in an M/H frame, the SCCC-encoded RS frame portions will be mapped in a time order (i.e., in a left-to-right direction).

Block Processor

Meanwhile, the block processor 302 performs an SCCC outer encoding process on the output of the M/H frame encoder 301. More specifically, the block processor 302 receives the data of each error correction encoded portion. Then, the block processor 302 encodes the data once again at a coding rate of 1/H (wherein H is an integer equal to or greater than 2 (i.e., H≧2)), thereby outputting the 1/H-rate encoded data to the group formatter 303. According to the embodiment of the present invention, the input data are encoded either at a coding rate of 1/2 (also referred to as “1/2-rate encoding”) or at a coding rate of 1/4 (also referred to as “1/4-rate encoding”). The data of each portion outputted from the M/H frame encoder 301 may include at least one of mobile service data, RS parity data, CRC data, and stuffing data. However, in a broader meaning, the data included in each portion may correspond to data for mobile services. Therefore, the data included in each portion will all be considered as mobile service data and described accordingly.

The group formatter 303 inserts the mobile service data SCCC-outer-encoded and outputted from the block processor 302 in the corresponding region within the data group, which is formed in accordance with a pre-defined rule. Also, in association with the data deinterleaving process, the group formatter 303 inserts various place holders (or known data place holders) in the corresponding region within the data group. Thereafter, the group formatter 303 deinterleaves the data within the data group and the place holders.

According to the present invention, with reference to data after being data-interleaved, as shown in FIG. 5, a data groups is configured of 10 M/H blocks (B1 to B10) and divided into 4 regions (A, B, C, and D).

Also, as shown in FIG. 5, when it is assumed that the data group is divided into a plurality of hierarchical regions, as described above, the block processor 302 may encode the mobile service data, which are to be inserted to each region based upon the characteristic of each hierarchical region, at different coding rates.

For example, the block processor 302 may encode the mobile service data, which are to be inserted in region A/B within the corresponding data group, at a coding rate of 1/2. Then, the group formatter 303 may insert the 1/2-rate encoded mobile service data to region A/B. Also, the block processor 302 may encode the mobile service data, which are to be inserted in region C/D within the corresponding data group, at a coding rate of 1/4 having higher (or stronger) error correction ability than the 1/2-coding rate. Thereafter, the group formatter 303 may insert the 1/2-rate encoded mobile service data to region C/D. In another example, the block processor 302 may encode the mobile service data, which are to be inserted in region C/D, at a coding rate having higher error correction ability than the 1/4-coding rate. Then, the group formatter 303 may either insert the encoded mobile service data to region C/D, as described above, or leave the data in a reserved region for future usage.

According to another embodiment of the present invention, the block processor 302 may perform a 1/H-rate encoding process in SCCC block units. Herein, the SCCC block includes at least one M/H block.

At this point, when 1/H-rate encoding is performed in M/H block units, the M/H blocks (B1 to B10) and the SCCC block (SCB1 to SCB10) become identical to one another (i.e., SCB1=B1, SCB2=B2, SCB3=B3, SCB4=B4, SCB5=B5, SCB6=B6, SCB7=B7, SCB8=B8, SCB9=B9, and SCB10=B10). For example, the M/H block 1 (B1) may be encoded at the coding rate of 1/2, the M/H block 2 (B2) may be encoded at the coding rate of 1/4, and the M/H block 3 (B3) may be encoded at the coding rate of 1/2. The coding rates are applied respectively to the remaining M/H blocks.

Alternatively, a plurality of M/H blocks within regions A, B, C, and D may be grouped into one SCCC block, thereby being encoded at a coding rate of 1/H in SCCC block units. Accordingly, the receiving performance of region C/D may be enhanced. For example, M/H block 1 (B1) to M/H block 5 (B5) may be grouped into one SCCC block and then encoded at a coding rate of 1/2. Thereafter, the group formatter 303 may insert the 1/2-rate encoded mobile service data to a section starting from M/H block 1 (B1) to M/H block 5 (B5).

Furthermore, M/H block 6 (B6) to M/H block 10 (B10) may be grouped into one SCCC block and then encoded at a coding rate of 1/4. Thereafter, the group formatter 303 may insert the 1/4-rate encoded mobile service data to another section starting from M/H block 6 (B6) to M/H block 10 (B10). In this case, one data group may consist of two SCCC blocks.

According to another embodiment of the present invention, one SCCC block may be formed by grouping two M/H blocks. For example, M/H block 1 (B1) and M/H block 6 (B16) may be grouped into one SCCC block (SCB1). Similarly, M/H block 2 (B2) and M/H block 7 (B7) may be grouped into another SCCC block (SCB2). Also, M/H block 3 (B3) and M/H block 8 (B8) may be grouped into another SCCC block (SCB3). And, M/H block 4 (B4) and M/H block 9 (B9) may be grouped into another SCCC block (SCB4). Furthermore, M/H block 5 (B5) and M/H block 10 (B10) may be grouped into another SCCC block (SCB5). In the above-described example, the data group may consist of 10 M/H blocks and 5 SCCC blocks. Accordingly, in a data (or signal) receiving environment undergoing frequent and severe channel changes, the receiving performance of regions C and D, which is relatively more deteriorated than the receiving performance of region A, may be reinforced. Furthermore, since the number of mobile service data symbols increases more and more from region A to region D, the error correction encoding performance becomes more and more deteriorated. Therefore, when grouping a plurality of M/H block to form one SCCC block, such deterioration in the error correction encoding performance may be reduced.

As described-above, when the block processor 302 performs encoding at a 1/H-coding rate, information associated with SCCC should be transmitted to the receiving system in order to accurately recover the mobile service data.

Table 7 below shows an example of a SCCC block mode, which indicating the relation between an M/H block and an SCCC block, among diverse SCCC block information.

TABLE 7 SCCC Block Mode 00 01 10 11 Description One M/H Block Two M/H Blocks per SCCC Block per SCCC Block SCB input, SCB input, SCB M/H Block M/H Blocks Reserved Reserved SCB1 B1 B1 + B6 SCB2 B2 B2 + B7 SCB3 B3 B3 + B8 SCB4 B4 B4 + B9 SCB5 B5 B5 + B10 SCB6 B6 — SCB7 B7 — SCB8 B8 — SCB9 B9 — SCB10 B10 —

More specifically, Table 4 shows an example of 2 bits being allocated in order to indicate the SCCC block mode. For example, when the SCCC block mode value is equal to ‘00’, this indicates that the SCCC block and the M/H block are identical to one another. Also, when the SCCC block mode value is equal to ‘01’, this indicates that each SCCC block is configured of 2 M/H blocks.

As described above, if one data group is configured of 2 SCCC blocks, although it is not indicated in Table 7, this information may also be indicated as the SCCC block mode. For example, when the SCCC block mode value is equal to ‘10’, this indicates that each SCCC block is configured of 5 M/H blocks and that one data group is configured of 2 SCCC blocks. Herein, the number of M/H blocks included in an SCCC block and the position of each M/H block may vary depending upon the settings made by the system designer. Therefore, the present invention will not be limited to the examples given herein. Accordingly, the SCCC mode information may also be expanded.

An example of a coding rate information of the SCCC block, i.e., SCCC outer code mode, is shown in Table 8 below.

TABLE 8 SCCC outer code mode (2 bits) Description 00 Outer code rate of SCCC block is ½ rate 01 Outer code rate of SCCC block is ¼ rate 10 Reserved 11 Reserved

More specifically, Table 8 shows an example of 2 bits being allocated in order to indicate the coding rate information of the SCCC block. For example, when the SCCC outer code mode value is equal to ‘00’, this indicates that the coding rate of the corresponding SCCC block is 1/2. And, when the SCCC outer code mode value is equal to ‘01’, this indicates that the coding rate of the corresponding SCCC block is 1/4.

If the SCCC block mode value of Table 7 indicates ‘00’, the SCCC outer code mode may indicate the coding rate of each M/H block with respect to each M/H block. In this case, since it is assumed that one data group includes 10 M/H blocks and that 2 bits are allocated for each SCCC block mode, a total of 20 bits are required for indicating the SCCC block modes of the 10 M/H modes.

In another example, when the SCCC block mode value of Table 7 indicates ‘00’, the SCCC outer code mode may indicate the coding rate of each region with respect to each region within the data group. In this case, since it is assumed that one data group includes 4 regions (i.e., regions A, B, C, and D) and that 2 bits are allocated for each SCCC block mode, a total of 8 bits are required for indicating the SCCC block modes of the 4 regions.

In another example, when the SCCC block mode value of Table 7 is equal to ‘01’, each of the regions A, B, C, and D within the data group has the same SCCC outer code mode.

Meanwhile, an example of an SCCC output block length (SOBL) for each SCCC block, when the SCCC block mode value is equal to ‘00’, is shown in Table 9 below.

TABLE 9 SIBL SCCC Block SOBL ½ rate ¼ rate SCB1 (B1) 528 264 132 SCB2 (B2) 1536 768 384 SCB3 (B3) 2376 1188 594 SCB4 (B4) 2388 1194 597 SCB5 (B5) 2772 1386 693 SCB6 (B6) 2472 1236 618 SCB7 (B7) 2772 1386 693 SCB8 (B8) 2508 1254 627 SCB9 (B9) 1416 708 354 SCB10 (B10) 480 240 120

More specifically, when given the SCCC output block length (SOBL) for each SCCC block, an SCCC input block length (SIBL) for each corresponding SCCC block may be decided based upon the outer coding rate of each SCCC block. The SOBL is equivalent to the number of SCCC output (or outer-encoded) bytes for each SCCC block. And, the SIBL is equivalent to the number of SCCC input (or payload) bytes for each SCCC block.

Table 10 below shows an example of the SOBL and SIBL for each SCCC block, when the SCCC block mode value is equal to ‘01’.

TABLE 10 SIBL SCCC Block SOBL ½ rate ¼ rate SCB1 (B1 + B6) 528 264 132 SCB2 (B2 + B7) 1536 768 384 SCB3 (B3 + B8) 2376 1188 594 SCB4 (B4 + B9) 2388 1194 597 SCB5 (B5 + B10) 2772 1386 693

In order to do so, as shown in FIG. 22, the block processor 302 includes a RS frame portion-SCCC block converter 511, a byte-bit converter 512, a convolution encoder 513, a symbol interleaver 514, a symbol-byte converter 515, and an SCCC block-M/H block converter 516.

The convolutional encoder 513 and the symbol interleaver 514 are virtually concatenated with the trellis encoding module in the post-processor in order to configure an SCCC block.

More specifically, the RS frame portion-SCCC block converter 511 divides the RS frame portions, which are being inputted, into multiple SCCC blocks using the SIBL of Table 9 and Table 10 based upon the RS code mode, SCCC block mode, and SCCC outer code mode. Herein, the M/H frame encoder 301 may output only primary RS frame portions or both primary RS frame portions and secondary RS frame portions in accordance with the RS frame mode.

When the RS Frame mode is set to ‘00’, a portion of the primary RS Frame equal to the amount of data, which are to be SCCC outer encoded and mapped to 10 M/H blocks (B1 to B10) of a data group, will be provided to the block processor 302. When the SCCC block mode value is equal to ‘00’, then the primary RS frame portion will be split into 10 SCCC Blocks according to Table 9. Alternatively, when the SCCC block mode value is equal to ‘01’, then the primary RS frame will be split into 5 SCCC blocks according to Table 10. When the RS frame mode value is equal to ‘01’, then the block processor 302 may receive two RS frame portions. The RS frame mode value of ‘01’ will not be used with the SCCC block mode value of ‘01’. The first portion from the primary RS frame will be SCCC-outer-encoded as SCCC Blocks SCB3, SCB4, SCB5, SCB6, SCB7, and SCB8 by the block processor 302. The SCCC Blocks SCB3 and SCB8 will be mapped to region B and the SCCC blocks SCB4, SCB5, SCB6, and SCB7 shall be mapped to region A by the group formatter 303. The second portion from the secondary RS frame will also be SCCC-outer-encoded, as SCB1, SCB2, SCB9, and SCB10, by the block processor 302. The group formatter 303 will map the SCCC blocks SCB1 and SCB10 to region D as the M/H blocks B1 and B10, respectively. Similarly, the SCCC blocks SCB2 and SCB9 will be mapped to region C as the M/H blocks B2 and B9.

The byte-bit converter 512 identifies the mobile service data bytes of each SCCC block outputted from the RS frame portion-SCCC block converter 511 as data bits, which are then outputted to the convolution encoder 513.

The convolution encoder 513 performs one of 1/2-rate encoding and 1/4-rate encoding on the inputted mobile service data bits.

FIG. 23 illustrates a detailed block diagram of the convolution encoder 513. The convolution encoder 513 includes two delay units 521 and 523 and three exclusive-or gates 522, 524, and 525. Herein, the convolution encoder 513 encodes an input data bit U and outputs the coded bit U to 5 bits (u0 to u4).

At this point, the input data bit U is directly outputted as uppermost bit u0 and simultaneously encoded as lower bit u1u2u3u4 and then outputted. More specifically, the input data bit U is directly outputted as the uppermost bit u0 and simultaneously outputted to the first and third exclusive-or gates 522 and 525. The first exclusive-or gate 522 performs exclusive-or operation on the input data bit U and the output bit of the first delay unit 521 and, then, outputs to the second delay unit 523. Then, the data bit delayed by a pre-determined time (e.g., by 1 clock) in the second delay unit 523 is outputted as a lower bit u1 and simultaneously fed-back to the first delay unit 521. The first delay unit 521 delays the data bit fed-back from the second delay unit 523 by a pre-determined time (e.g., by 1 clock). Then, the first delay unit 521 outputs the delayed data bit as a lower bit u2 and, at the same time, outputs the fed-back data to the first exclusive-or gate 522 and the second exclusive-or gate 524.

The second exclusive-or gate 524 performs exclusive-or operation on the data bits outputted from the first and second delay units 521 and 523 and outputs as a lower bit u3. The third exclusive-or gate 525 performs on exclusive-or operation on the input data bit U and the output of the second delay unit 523 and outputs as a lower bit u4.

At this point, the first and second delay units 521 and 523 are reset to ‘0’, at the starting point of each SCCC block. The convolution encoder 513 of FIG. 23 may be used as a 1/2-rate encoder or a 1/4-rate encoder.

More specifically, when a portion of the output bit of the convolution encoder 513, shown in FIG. 23, is selected and outputted, the convolution encoder 513 may be used as one of a 1/2-rate encoder and a 1/4-rate encoder.

Table 11 below shown an example of output symbols of the convolution encoder 513.

TABLE 11 ¼ rate Region ½ rate SCCC block mode = ‘00’ SCCC block mode = ‘01’ A, B (u0, u1) (u0, u2), (u1, u3) (u0, u2), (u1, u4) C, D (u0, u1), (u3, u4)

For example, at the 1/2-coding rate, 1 output symbol (i.e., u0 and u1 bits) may be selected and outputted. And, at the 1/4-coding rate, depending upon the SCCC block mode, 2 output symbols (i.e., 4 bits) may be selected and outputted. For example, when the SCCC block mode value is equal to ‘01’, and when an output symbol configured of u0 and u2 and another output symbol configured of u1 and u4 are selected and outputted, a 1/4-rate coding result may be obtained.

The mobile service data encoded at the coding rate of 1/2 or 1/4 by the convolution encoder 513 are outputted to the symbol interleaver 514.

The symbol interleaver 514 performs block interleaving, in symbol units, on the output data symbol of the convolution encoder 513. More specifically, the symbol interleaver 514 is a type of block interleaver. Any interleaver performing structural rearrangement (or realignment) may be applied as the symbol interleaver 514 of the block processor. However, in the present invention, a variable length symbol interleaver that can be applied even when a plurality of lengths is provided for the symbol, so that its order may be rearranged, may also be used.

FIG. 24 illustrates a symbol interleaver according to an embodiment of the present invention. Particularly, FIG. 30 illustrates an example of the symbol interleaver when B=2112 and L=4096.

Herein, B indicates a block length in symbols that are outputted for symbol interleaving from the convolution encoder 513. And, L represents a block length in symbols that are actually interleaved by the symbol interleaver 514. At this point, the block length in symbols B inputted to the symbol interleaver 514 is equivalent to 4×SOBL. More specifically, since one symbol is configured of 2 bits, the value of B may be set to be equal to 4×SOBL.

In the present invention, when performing the symbol-interleaving process, the conditions of L=2^(m) (wherein m is an integer) and of L≧B should be satisfied. If there is a difference in value between B and L, (L−B) number of null (or dummy) symbols is added, thereby creating an interleaving pattern, as shown in P*(i) of FIG. 24.

Therefore, B becomes a block size of the actual symbols that are inputted to the symbol interleaver 514 in order to be interleaved. L becomes an interleaving unit when the interleaving process is performed by an interleaving pattern created from the symbol interleaver 514.

Equation 5 shown below describes the process of sequentially receiving B number of symbols, the order of which is to be rearranged, and obtaining an L value satisfying the conditions of L=2^(m) (wherein m is an integer) and of L≧B, thereby creating the interleaving so as to realign (or rearrange) the symbol order.

Equation 5

In relation to all places, wherein 0≦i≦B−1,

P′(i)={89×i×(i+1)/2} mod L

Herein, L≧B, L=2^(m), wherein m is an integer.

As shown in P′(i) of FIG. 24 and Equation 5, the order of B number of input symbols and (L−B) number of null symbols is rearranged by using the above-mentioned Equation 6. Then, as shown in P(i) of FIG. 24, the null byte places are removed, so as to rearrange the order. Starting with the lowest value of i, the P(i) are shifted to the left in order to fill the empty entry locations. Thereafter, the symbols of the aligned interleaving pattern P(i) are outputted to the symbol-byte converter 515 in order.

Herein, the symbol-byte converter 515 converts to bytes the mobile service data symbols, having the rearranging of the symbol order completed and then outputted in accordance with the rearranged order, and thereafter outputs the converted bytes to the SCCC block-M/H block converter 516. The SCCC block-M/H block converter 516 converts the symbol-interleaved SCCC blocks to M/H blocks, which are then outputted to the group formatter 303.

If the SCCC block mode value is equal to ‘00’, the SCCC block is mapped at a one-to-one (1:1) correspondence with each M/H block within the data group. In another example, if the SCCC block mode value is equal to ‘01’, each SCCC block is mapped with two M/H blocks within the data group. For example, the SCCC block SCB1 is mapped with (B1, B6), the SCCC block SCB2 is mapped with (B2, B7), the SCCC block SCB3 is mapped with (B3, B8), the SCCC block SCB4 is mapped with (B4, B9), and the SCCC block SCB5 is mapped with (B5, B10). The M/H block that is outputted from the SCCC block-M/H block converter 516 is configured of mobile service data and FEC redundancy. In the present invention, the mobile service data as well as the FEC redundancy of the M/H block will be collectively considered as mobile service data.

Group Formatter

The group formatter 303 inserts data of M/H blocks outputted from the block processor 302 to the corresponding M/H blocks within the data group, which is formed in accordance with a pre-defined rule. Also, in association with the data-deinterleaving process, the group formatter 303 inserts various place holders (or known data place holders) in the corresponding region within the data group.

More specifically, apart from the encoded mobile service data outputted from the block processor 302, the group formatter 303 also inserts MPEG header place holders, non-systematic RS parity place holders, main service data place holders, which are associated with the data deinterleaving in a later process, as shown in FIG. 5. Herein, the main service data place holders are inserted because the mobile service data bytes and the main service data bytes are alternately mixed with one another in regions B to D based upon the input of the data deinterleaver, as shown in FIG. 5. For example, based upon the data outputted after data deinterleaving, the place holder for the MPEG header may be allocated at the very beginning of each packet. Also, in order to configure an intended group format, dummy bytes may also be inserted. Furthermore, the group formatter 303 inserts initialization data (i.e., trellis initialization byte) of the trellis encoding module 256 in the corresponding regions. For example, the initialization data may be inserted in the beginning of the known data sequence. The initialization data is used for initializing memories within the trellis encoding module 256, and is not transmitted to the receiving system.

Additionally, the group formatter 303 may also insert signaling information, which are encoded and outputted from the signaling encoder 304, in corresponding regions within the data group.

At this point, reference may be made to the signaling information when the group formatter 303 inserts each data type and respective place holders in the data group. The process of encoding the signaling information and inserting the encoded signaling information to the data group will be described in detail in a later process.

After inserting each data type and respective place holders in the data group, the group formatter 303 may deinterleave the data and respective place holders, which have been inserted in the data group, as an inverse process of the data interleaver, thereby outputting the deinterleaved data and respective place holders to the packet formatter 305. The group formatter 303 may include a group format organizer 527, and a data deinterleaver 529, as shown in FIG. 25. The group format organizer 527 inserts data and respective place holders in the corresponding regions within the data group, as described above. And, the data deinterleaver 529 deinterleaves the inserted data and respective place holders as an inverse process of the data interleaver.

The packet formatter 305 removes the main service data place holders and the RS parity place holders and replaces the MPEG header place holders with MPEG header that were allocated for the deinterleaving process from the deinterleaved data being inputted.

Also, when the group formatter 303 inserts known data place holders, the packet formatter 303 may insert actual known data in the known data place holders, or may directly output the known data place holders without any modification in order to make replacement insertion in a later process.

Thereafter, the packet formatter 305 identifies the data within the packet-formatted data group, as described above, as a 188-byte unit mobile service data packet (i.e., MPEG TS packet), which is then provided to the packet multiplexer 240.

The packet multiplexer 240 multiplexes the mobile service data packets packet-formatted and outputted from the packet formatter 306 and main service data packets outputted from the packet jitter mitigator 220. Then, the packet multiplexer 240 outputs the multiplexed data packets to the data randomizer 251 of the post-processor 250. If the packet multiplexer 240 receives 118 mobile service data packets from the packet formatter 305, 37 mobile service data packets are placed before a place for inserting VSB field synchronization. Then, the remaining 81 mobile service data packets are placed after the place for inserting VSB field synchronization. The multiplexing method may be adjusted by diverse variables of the system design. The multiplexing method and multiplexing rule of the packet multiplexer 240 will be described in more detail in a later process.

Also, since a data group including mobile service data in-between the data bytes of the main service data is multiplexed (or allocated) during the packet multiplexing process, the shifting of the chronological position (or place) of the main service data packet becomes relative. Also, a system object decoder (i.e., MPEG decoder) for processing the main service data of the receiving system, receives and decodes only the main service data and recognizes the mobile service data packet as a null data packet.

Therefore, when the system object decoder of the receiving system receives a main service data packet that is multiplexed with the data group, a packet jitter occurs.

At this point, since a multiple-level buffer for the video data exists in the system object decoder and the size of the buffer is relatively large, the packet jitter generated from the packet multiplexer 240 does not cause any serious problem in case of the video data. However, since the size of the buffer for the audio data in the object decoder is relatively small, the packet jitter may cause considerable problem.

More specifically, due to the packet jitter, an overflow or underflow may occur in the buffer for the main service data of the receiving system (e.g., the buffer for the audio data).

Therefore, the packet jitter mitigator 220 re-adjusts the relative position of the main service data packet so that the overflow or underflow does not occur in the system object decoder.

In the present invention, examples of repositioning places for the audio data packets within the main service data in order to minimize the influence on the operations of the audio buffer will be described in detail. The packet jitter mitigator 220 repositions the audio data packets in the main service data section so that the audio data packets of the main service data can be as equally and uniformly aligned and positioned as possible.

Additionally, when the positions of the main service data packets are relatively re-adjusted, associated program clock reference (PCR) values may also be modified accordingly. The PCR value corresponds to a time reference value for synchronizing the time of the MPEG decoder. Herein, the PCR value is inserted in a specific region of a TS packet and then transmitted. In the example of the present invention, the packet jitter mitigator 220 also performs the operation of modifying the PCR value.

The output of the packet jitter mitigator 220 is inputted to the packet multiplexer 240. As described above, the packet multiplexer 240 multiplexes the main service data packets outputted from the packet jitter mitigator 220 with the mobile service data packets outputted from the pre-processor 230 into a burst structure in accordance with a pre-determined multiplexing rule. Then, the packet multiplexer 240 outputs the multiplexed data packets to the data randomizer 251 of the post-processor 250.

If the inputted data correspond to the main service data packet, the data randomizer 251 performs the same randomizing process as that of the conventional randomizer and outputs to the RS encoder/non-systematic RS encoder 252. More specifically, all data bytes of the main service data packet are randomized by using a pseudo random byte generated from the data randomizer 251. Thereafter, the randomized data are outputted to the RS encoder/non-systematic RS encoder 252. On the other hand, if the inputted data correspond to the mobile service data packet, the data randomizer 251 performs randomizing only MPEG header byte of the mobile service data packet and outputs to the RS encoder/non-systematic RS encoder 252. The randomizing of the mobile service data included in the mobile service data packet was performed by the data randomizer 411 of the primary encoder 410 and/or the data randomizer 422 of the secondary encoder 420.

The RS encoder/non-systematic RS encoder 252 performs an RS encoding process on the data being randomized by the data randomizer 251 or on the data bypassing the data randomizer 251, so as to add 20 bytes of RS parity data. Thereafter, the processed data are outputted to the data interleaver 253. Herein, if the inputted data correspond to the main service data packet, the RS encoder/non-systematic RS encoder 252 performs the same systematic RS encoding process as that of the conventional broadcasting system, thereby adding the 20-byte RS parity data at the end of the 187-byte data. Alternatively, if the inputted data correspond to the mobile service data packet, the RS encoder/non-systematic RS encoder 252 performs a non-systematic RS encoding process. At this point, the 20-byte RS parity data obtained from the non-systematic RS encoding process are inserted in a pre-decided parity byte place within the mobile service data packet.

The data interleaver 253 corresponds to a byte unit convolutional interleaver.

The output of the data interleaver 253 is inputted to the parity replacer 254 and to the non-systematic RS encoder 255.

Meanwhile, a process of initializing a memory within the trellis encoding module 256 is primarily required in order to decide the output data of the trellis encoding module 256, which is located after the parity replacer 254, as the known data pre-defined according to an agreement between the receiving system and the transmitting system. More specifically, the memory of the trellis encoding module 256 should first be initialized before the received known data sequence is trellis-encoded.

At this point, the beginning portion of the known data sequence that is received corresponds to the initialization data (i.e., trellis initialization data bytes) and not to the actual known data. Herein, the initialization data has been included in the data by the group formatter within the pre-processor 230 in an earlier process. Therefore, the process of replacing the initialization data with memory values within the trellis encoding module 256 are required to be performed immediately before the inputted known data sequence is trellis-encoded.

More specifically, the initialization data are replaced with the memory value within the trellis encoding module 256, thereby being inputted to the trellis encoding module 256. At this point, the memory value replacing the initialization data are process with (or calculated by) an exclusive OR (XOR) operation with the respective memory value within the trellis encoding module 256, so as to be inputted to the corresponding memory. Therefore, the corresponding memory is initialized to ‘0’. Additionally, a process of using the memory value replacing the initialization data to re-calculate the RS parity, so that the re-calculated RS parity value can replace the RS parity being outputted from the data interleaver 253, is also required.

Therefore, the non-systematic RS encoder 255 receives the mobile service data packet including the initialization data from the data interleaver 253 and also receives the memory value from the trellis encoding module 256. Among the inputted mobile service data packet, the initialization data are replaced with the memory value, and the RS parity data that are added to the mobile service data packet are removed and processed with non-systematic RS encoding. Thereafter, the new RS parity obtained by performing the non-systematic RS encoding process is outputted to the parity replacer 255. Accordingly, the parity replacer 255 selects the output of the data interleaver 253 as the data within the mobile service data packet, and the parity replacer 255 selects the output of the non-systematic RS encoder 255 as the RS parity. The selected data are then outputted to the trellis encoding module 256.

Meanwhile, if the main service data packet is inputted or if the mobile service data packet, which does not include any initialization data that are to be replaced, is inputted, the parity replacer 254 selects the data and RS parity that are outputted from the data interleaver 253. Then, the parity replacer 254 directly outputs the selected data to the trellis encoding module 256 without any modification.

The trellis encoding module 256 converts the byte-unit data to symbol units and performs a 12-way interleaving process so as to trellis-encode the received data. Thereafter, the processed data are outputted to the synchronization multiplexer 260.

FIG. 26 illustrates a detailed diagram of one of 12 trellis encoders included in the trellis encoding module 256. Herein, the trellis encoder includes first and second multiplexers 531 and 541, first and second exclusive OR (XOR) gates 532 and 542, and first to third memories 533, 542, and 544.

More specifically, the first to third memories 533, 542, and 544 are initialized by the memory value instead of the initialization data from the parity replacer 254. More specifically, when the first symbol (i.e., two bits), which are converted from initialization data (i.e., each trellis initialization data byte), are inputted, the input bits of the trellis encoder will be replaced by the memory values of the trellis encoder, as shown in FIG. 26.

Since 2 symbols (i.e., 4 bits) are required for trellis initialization, the last 2 symbols (i.e., 4 bits) from the trellis initialization bytes are not used for trellis initialization and are considered as a symbol from a known data byte and processed accordingly.

When the trellis encoder of FIG. 26 is in the initialization mode, the input comes from an internal trellis status (or state) and not from the parity replacer 254. When the trellis encoder is in the normal mode, the input symbol (X2X1) provided from the parity replacer 254 will be processed. The trellis encoder provides the converted (or modified) input data for trellis initialization to the non-systematic RS encoder 255.

More specifically, when a selection signal designates a normal mode, the first multiplexer 531 selects an upper bit X2 of the input symbol. And, when a selection signal designates an initialization mode, the first multiplexer 531 selects the output of the first memory 533 and outputs the selected output data to the first XOR gate 532. The first XOR gate 532 performs XOR operation on the output of the first multiplexer 531 and the output of the first memory 533, thereby outputting the added result to the first memory 533 and, at the same time, as a most significant (or uppermost) bit Z2. The first memory 533 delays the output data of the first XOR gate 532 by 1 clock, thereby outputting the delayed data to the first multiplexer 531 and the first XOR gate 532. Meanwhile, when a selection signal designates a normal mode, the second multiplexer 541 selects a lower bit X1 of the input symbol. And, when a selection signal designates an initialization mode, the second multiplexer 541 selects the output of the second memory 542, thereby outputting the selected result to the second XOR gate 543 and, at the same time, as a lower bit Z1. The second XOR gate 543 performs XOR operation on the output of the second multiplexer 541 and the output of the second memory 542, thereby outputting the added result to the third memory 544. The third memory 544 delays the output data of the second XOR gate 543 by 1 clock, thereby outputting the delayed data to the second memory 542 and, at the same time, as a least significant (or lowermost) bit Z0. The second memory 542 delays the output data of the third memory 544 by 1 clock, thereby outputting the delayed data to the second XOR gate 543 and the second multiplexer 541.

The select signal designates an initialization mode during the first two symbols that are converted from the initialization data.

For example, when the select signal designates an initialization mode, the first XOR gate 532 performs an XOR operation on the value of the first memory 533, which is provided through the first multiplexer 531, and on a memory value that is directly provided from the first memory 533. That is, the first XOR gate 532 performs an XOR operation on 2 bits having the same value. Generally, when only one of the two bits belonging to the operand is ‘1’, the result of the XOR gate is equal to ‘1’. Otherwise, the result of the XOR gate becomes equal to ‘0’. Therefore, when the value of the first memory 533 is processed with an XOR operation, the result is always equal to ‘0’. Furthermore, since the output of the first XOR gate 532, i.e., ‘0’, is inputted to the first memory 533, the first memory 533 is initialized to ‘0’.

Similarly, when the select signal designates an initialization mode, the second XOR gate 543 performs an XOR operation on the value of the second memory 542, which is provided through the second multiplexer 541, and on a memory value that is directly provided from the second memory 542. Therefore, the output of the second XOR gate 543 is also always equal to ‘0’. Since the output of the second XOR gate 543, i.e., ‘0’, is inputted to the third memory 544, the third memory 544 is also initialized to ‘0’. The output of the third memory 544 is inputted to the second memory 542 in the next clock, thereby initializing the second memory 542 to ‘0’. In this case also, the select signal designates the initialization mode.

More specifically, when the first symbol being converted from the initialization data byte replaces the values of the first memory 533 and the second memory 542, thereby being inputted to the trellis encoder, each of the first and third memories 533 and 544 within the trellis encoder is initialized to ‘00’. Following the process, when the second symbol being converted from the initialization data byte replaces the values of the first memory 533 and the second memory 542, thereby being inputted to the trellis encoder, each of the first, second, and third memories 533, 542, and 544 within the trellis encoder is initialized to ‘000’. As described above, 2 symbols are required to initialize the memory of the trellis encoder. At this point, while the select signal designates an initialization mode, the output bits (X2′X1′) of the first and second memories 533 and 542 are inputted to the non-systematic RS encoder 255, so as to perform a new RS parity calculation process.

The synchronization multiplexer 260 inserts a field synchronization signal and a segment synchronization signal to the data outputted from the trellis encoding module 256 and, then, outputs the processed data to the pilot inserter 271 of the transmission unit 270.

Herein, the data having a pilot inserted therein by the pilot inserter 271 are modulated by the modulator 272 in accordance with a pre-determined modulating method (e.g., a VSB method). Thereafter, the modulated data are transmitted to each receiving system though the radio frequency (RF) up-converter 273.

Assignment of Known Data (or Training Signal)

The transmission system inserts long and regularly spaced training sequences (i.e., known data sequences) into each data group. Each data group contains 6 training sequences. The training sequences are specified before trellis-encoding. The training sequences are then trellis-encoded and these trellis-encoded sequences also are known sequences. This is because the trellis encoder memories are initialized to pre-determined values at the beginning of each sequence. The form of the 6 training sequences at the byte level (before trellis-encoding) is shown in FIG. 27. FIG. 27 is an embodiment of the arrangement of the training sequences that is performed by the group formatter 303.

The 1^(st) training sequence is located at the last 2 segments of the 3^(rd) M/H block (B3). The 2^(nd) training sequence may be inserted at the 2^(nd) and 3^(rd) segments of the 4^(th) M/H block (B4). The 2^(nd) training sequence is next to the signaling area, as shown in FIG. 5. Then, the 3^(rd) training sequence, the 4^(th) training sequence, the 5^(th) training sequence, and the 6^(th) training sequence may be placed at the last 2 segments of the 4^(th), 5^(th), 6^(th), and 7^(th) M/H blocks (B4, B5, B6, and B7), respectively.

As shown in FIG. 27, the 1^(st) training sequence, the 3^(rd) training sequence, the 4^(th) training sequence, the 5^(th) training sequence, and the 6^(th) training sequence are spaced 16 segments apart from one another. Referring to FIG. 27, the dotted area indicates trellis initialization data bytes, the lined area indicates training data bytes, and the white area includes other bytes such as the FEC-coded M/H service data bytes, FEC-coded signaling data, main service data bytes, RS parity data bytes (for backwards compatibility with legacy ATSC receivers) and/or dummy data bytes.

FIG. 28 illustrates the training sequences (at the symbol level) after trellis-encoding by the trellis encoder. Referring to FIG. 28, the dotted area indicates data segment sync symbols, the lined area indicates training data symbols, and the white area includes other symbols, such as FEC-coded mobile service data symbols, FEC-coded signaling data symbols, main service data symbols, RS parity data symbols, dummy data symbols, trellis initialization data symbols, and/or the first part of the training sequence data symbols.

After the trellis-encoding process, the last 1416 (=588+828) symbols of the 1^(st) training sequence, the 3^(rd) training sequence, the 4^(th) training sequence, the 5^(th) training sequence, and the 6^(th) training sequence commonly share the same data pattern. The 2^(nd) training sequence has a first 528-symbol sequence and a second 528-symbol sequence that have the same data pattern.

More specifically, the 528-symbol sequence is repeated after the 4-symbol data segment synchronization signal. At the end of each training sequence, the memory contents of the twelve modified trellis encoders shall be set to zero (0).

Processing Signaling Information

The present invention assigns signaling information areas for inserting signaling information to some areas within each data group.

FIG. 29 illustrates an example of assigning signaling information areas for inserting signaling information starting from the 1^(st) segment of the 4^(th) M/H block (B4) to a portion of the 2^(nd) segment. More specifically, 276(=207+69) bytes of the 4^(th) M/H block (B4) in each data group are assigned as the signaling information area. In other words, the signaling information area consists of 207 bytes of the 1^(st) segment and the first 69 bytes of the 2^(nd) segment of the 4^(th) M/H block (B4). For example, the 1^(st) segment of the 4^(th) M/H block (B4) corresponds to the 17^(th) or 173^(rd) segment of a VSB field.

For example, when the data group includes 6 known data sequences, as shown in FIG. 27 and FIG. 28, the signaling information area is located between the first known data sequence and the second known data sequence. More specifically, the first known data sequence is inserted in the last 2 segments of the 3^(rd) M/H block (B3), and the second known data sequence in inserted in the 2^(nd) and 3^(rd) segments of the 4^(th) M/H block (B4). Furthermore, the 3^(rd) to 6^(th) known data sequences are respectively inserted in the last 2 segments of each of the 4^(th), 5^(th), 6^(th), and 7^(th) M/H blocks (B4, B5, B6, and B7). The 1^(st) and 3^(rd) to 6^(th) known data sequences are spaced apart by 16 segments.

The signaling information that is to be inserted in the signaling information area is FEC-encoded by the signaling encoder 304, thereby inputted to the group formatter 303.

The group formatter 303 inserts the signaling information, which is FEC-encoded and outputted by the signaling encoder 304, in the signaling information area within the data group.

Herein, the signaling information may be identified by two different types of signaling channels: a transmission parameter channel (TPC) and a fast information channel (FIC).

Herein, the TPC data is transmitted through the TPC and corresponds to signaling information including transmission parameters, such as RS frame information, RS encoding information, FIC information, data group information, SCCC information, and M/H frame information and so on. However, the TPC data presented herein is merely exemplary. And, since the adding or deleting of signaling information included in the TPC may be easily adjusted and modified by one skilled in the art, the present invention will, therefore, not be limited to the examples set forth herein. Also, the TPC data includes parameters that are mostly used in a physical layer module. And, since the TPC data are transmitted without being interleaved, the TPC data may be accessed by slot unit in the receiving system.

Furthermore, the FIC data is transmitted through the FIC and is provided to enable a fast service acquisition of data receivers, and the FIC data includes cross layer information between the physical layer and the upper layer(s).

FIG. 30 illustrates a detailed block diagram of the signaling encoder 304 according to the present invention.

Referring to FIG. 34, the signaling encoder 304 includes a TPC encoder 561, an FIC encoder 562, a block interleaver 563, a multiplexer 564, a signaling randomizer 565, and an iterative turbo encoder 566.

The TPC encoder 561 receives 10-bytes of TPC data and performs (18,10)-RS encoding on the 10-bytes of TPC data, thereby adding 8 bytes of RS parity data to the 10 bytes of TPC data. The 18 bytes of RS-encoded TPC data are outputted to the multiplexer 564.

The FIC encoder 562 receives 37-bytes of FIC data and performs (51,37)-RS encoding on the 37-bytes of FIC data, thereby adding 14 bytes of RS parity data to the 37 bytes of FIC data. Thereafter, the 51 bytes of RS-encoded FIC data are inputted to the block interleaver 563, thereby being interleaved in predetermined block units. Herein, the block interleaver 563 corresponds to a variable length block interleaver. The block interleaver 563 interleaves the FIC data within each sub-frame in TNoG(column)×51(row) block units and then outputs the interleaved data to the multiplexer 564. Herein, the TNoG corresponds to the total number of data groups being assigned to a sub-frame. The block interleaver 563 is synchronized with the first set of FIC data in each sub-frame.

The block interleaver 563 writes 51 bytes of incoming (or inputted) RS codewords in a row direction (i.e., row-by-row) and left-to-right and up-to-down directions and reads 51 bytes of RS codewords in a column direction (i.e., column-by-column) and left-to-right and up-to-down directions, thereby outputting the RS codewords.

The multiplexer 564 multiplexes the RS-encoded TPC data from the TPC encoder 561 and the block-interleaved FIC data from the block interleaver 563 along a time axis. Then, the multiplexer 564 outputs 69 bytes of the multiplexed data to the signaling randomizer 565.

The signaling randomizer 565 randomizes the multiplexed data and outputs the randomized data to the iterative turbo encoder 566. The signaling randomizer 565 may use the same generator polynomial of the randomizer used for mobile service data. Also, initialization occurs in each data group.

The iterative turbo encoder 566 corresponds to an inner encoder performing iterative turbo encoding in a PCCC method on the randomized data (i.e., signaling information data). The iterative turbo encoder 566 may include 6 even component encoders and 6 odd component encoders.

FIG. 31 illustrates an example of a syntax structure of TPC data being inputted to the TPC encoder 561.

The TPC data are inserted in the signaling information area of each data group and then transmitted. The TPC data may include a sub-frame_number field, a slot_number field, a parade_id field, a starting_group_number (SGN) field, a number_of_groups (NoG) field, a parade_repetition_cycle (PRC) field, an RS_frame_mode field, an RS_code_mode_primary field, an RS_code_mode_secondary field, an SCCC_block_mode field, an SCCC_outer_code_mode_A field, an SCCC_outer_code_mode_B field, an SCCC_outer_code_mode_C field, an SCCC_outer_code_mode_D field, an FIC_version field, a parade_continuity_counter field, and a TNoG field.

The Sub-Frame_number field corresponds to the current Sub-Frame number within the M/H frame, which is transmitted for M/H frame synchronization. The value of the Sub-Frame_number field may range from 0 to 4.

The Slot_number field indicates the current slot number within the sub-frame, which is transmitted for M/H frame synchronization. Also, the value of the Sub-Frame_number field may range from 0 to 15.

The Parade_id field identifies the parade to which this group belongs. The value of this field may be any 7-bit value. Each parade in a M/H transmission shall have a unique Parade_id field. Communication of the Parade_id between the physical layer and the management layer may be performed by means of an Ensemble_id field formed by adding one bit to the left of the Parade_id field. If the Ensemble_id field is used for the primary Ensemble delivered through this parade, the added MSB shall be equal to ‘0’. Otherwise, if the Ensemble_id field is used for the secondary ensemble, the added MSB shall be equal to ‘1’. Assignment of the Parade_id field values may occur at a convenient level of the system, usually in the management layer.

The starting_group_number (SGN) field shall be the first Slot_number for a parade to which this group belongs, as determined by Equation 1 (i.e., after the Slot numbers for all preceding parades have been calculated). The SGN and NoG shall be used according to Equation 1 to obtain the slot numbers to be allocated to a parade within the sub-frame.

The number_of Groups (NoG) field shall be the number of groups in a sub-frame assigned to the parade to which this group belongs, minus 1, e.g., NoG=0 implies that one group is allocated (or assigned) to this parade in a sub-frame. The value of NoG may range from 0 to 7. This limits the amount of data that a parade may take from the main (legacy) service data, and consequently the maximum data that can be carried by one parade. The slot numbers assigned to the corresponding Parade can be calculated from SGN and NoG, using Equation 1. By taking each parade in sequence, the specific slots for each parade will be determined, and consequently the SGN for each succeeding parade. For example, if for a specific parade SGN=3 and NoG=3 (010b for 3-bit field of NoG), substituting i=3, 4, and 5 in Equation 1 provides slot numbers 12, 2, and 6.

The Parade_repetition_cycle (PRC) field corresponds to the cycle time over which the parade is transmitted, minus 1, specified in units of M/H frames, as described in Table 12.

TABLE 12 PRC Description 000 This parade shall be transmitted once every M/H frame. 001 This parade shall be transmitted once every 2 M/H frames. 010 This parade shall be transmitted once every 3 M/H frames. 011 This parade shall be transmitted once every 4 M/H frames. 100 This parade shall be transmitted once every 5 M/H frames. 101 This parade shall be transmitted once every 6 M/H frames. 110 This parade shall be transmitted once every 7 M/H frames. 111 Reserved

For example, if PRC field value is equal to ‘001’, this indicates that the parade shall be transmitted once every 2 M/H frame.

The RS_Frame_mode field shall be as defined in Table 1. The RS_Frame_mode field represents that one parade transmits one RS frame or two RS frames.

The RS_code_mode_primary field shall be the RS code mode for the primary RS frame. Herein, the RS_code_mode_primary field is defined in Table 6.

The RS_code_mode_secondary field shall be the RS code mode for the secondary RS frame. Herein, the RS_code_mode_secondary field is defined in Table 6.

The SCCC_Block_mode field represents how M/H blocks within a data group are assigned to SCCC block. The SCCC_Block_mode field shall be as defined in Table 7.

The SCCC_outer_code_mode_A field corresponds to the SCCC outer code mode for Region A within a data group. The SCCC outer code mode is defined in Table 8.

The SCCC_outer_code_mode_B field corresponds to the SCCC outer code mode for Region B within the data group.

The SCCC_outer_code_mode_C field corresponds be the SCCC outer code mode for Region C within the data group.

And, the SCCC_outer_code_mode_D field corresponds to the SCCC outer code mode for Region D within the data group.

The FIC_version field represents a version of FIC data.

The Parade_continuity_counter field counter may increase from 0 to 15 and then repeat its cycle. This counter shall increment by 1 every (PRC+1) M/H frames. For example, as shown in Table 12, PRC=011 (decimal 3) implies that Parade_continuity_counter increases every fourth M/H frame.

The TNoG field may be identical for all sub-frames in an M/H Frame.

However, the information included in the TPC data presented herein is merely exemplary. And, since the adding or deleting of information included in the TPC may be easily adjusted and modified by one skilled in the art, the present invention will, therefore, not be limited to the examples set forth herein.

Since the TPC data (excluding the Sub-Frame_number field and the Slot_number field) for each parade do not change their values during an M/H frame, the same information is repeatedly transmitted through all M/H groups belonging to the corresponding parade during an M/H frame. This allows very robust and reliable reception of the TPC data. Because the Sub-Frame_number and the Slot_number are increasing counter values, they also are robust due to the transmission of regularly expected values. Furthermore, the FIC data is provided to enable a fast service acquisition of data receivers, and the FIC information includes cross layer information between the physical layer and the upper layer(s).

FIG. 32 illustrates an example of a transmission scenario of the TPC data and the FIC data. The values of the Sub-Frame_number field, Slot_number field, Parade_id field, Parade_repetition_cycle field, and Parade_continuity_counter field may corresponds to the current M/H frame throughout the 5 sub-frames within a specific M/H frame. Some of TPC parameters and FIC data are signaled in advance.

The SGN, NoG and all FEC modes may have values corresponding to the current M/H frame in the first two sub-frames. The SGN, NoG and all FEC modes may have values corresponding to the frame in which the parade next appears throughout the 3^(rd), 4^(th) and 5^(th) sub-frames of the current M/H frame. This enables the M/H receivers to receive (or acquire) the transmission parameters in advance very reliably.

For example, when Parade_repetition_cycle=‘000’, the values of the 3^(rd), 4^(th), and 5^(th) sub-frames of the current M/H frame correspond to the next M/H frame. Also, when Parade_repetition_cycle=‘011’, the values of the 3^(rd), 4^(th), and 5^(th) sub-frames of the current M/H frame correspond to the 4^(th) M/H frame and beyond.

The FIC_version field and the FIC_data field may have values that apply to the current M/H Frame during the 1^(st) sub-frame and the 2^(nd) sub-frame, and they shall have values corresponding to the M/H frame immediately following the current M/H frame during the 3^(rd), 4^(th), and 5^(th) sub-frames of the current M/H frame.

Meanwhile, FIC data being transmitted through the FIC, i.e., an FIC chunk uses its fast characteristic so as to deliver mapping (or binding) information between a mobile service and an ensemble to the receiving system. More specifically, the FIC chunk corresponds to signaling data used for enabling the receiving system to swiftly find an ensemble that delivers a wanted (or desired) mobile service and to swiftly receive RS frames of the corresponding ensemble. At this point, the FIC chunk is segmented into a plurality of FIC segment payloads and a plurality of FIC segments are formed by added each FIC segment header to each FIC segment payload. Furthermore, one FIC segment is transmitted through one data group.

FIG. 33 illustrates a syntax structure of an FIC chunk that maps the relation between a mobile service and an ensemble through the FIC.

Herein, the FIC chunk consists of a 5-byte FIC chunk header and an FIC chunk payload having variable-length.

FIG. 34 illustrates a syntax structure of an FIC chunk header according to an embodiment of the present invention.

Herein, the FIC chunk header signals a non-backward compatible major protocol version change in a corresponding FIC chunk and also signals a backward compatible minor protocol version change. Furthermore, the FIC chunk header also signals the length for an extension of an FIC chunk header, the length for an extension of an ensemble loop header, and the length for an extension of a mobile service loop that can be generated by a minor protocol version change.

According to an embodiment of the present invention, a receiver (or receiving system) that can adopt the corresponding minor protocol version change may process the corresponding extension field, whereas a legacy (or conventional) receiver that cannot adopt the corresponding minor protocol version change may skip the corresponding extension field by using each of the corresponding length information. For example, in case of a receiving system that can accept the corresponding minor protocol version change, the directions given in the corresponding extension field may be known. Furthermore, the receiving system may perform operations in accordance with the directions given in the corresponding extension field.

According to an embodiment of the present invention, a minor protocol version change in the FIC chunk is performed by inserting additional fields at the respective end portion of the FIC chunk header, the ensemble loop header, and the mobile service loop included in the previous minor protocol version FIC chunk. According to an embodiment of the present invention, in any other case, or when the length of the additional fields cannot be expressed (or indicated) by each extension length within the FIC chunk header, or when a specific field within the FIC chunk payload is missing (or cannot be found), or when the number of bits being assigned to the corresponding field or the definition of the corresponding field is changed (or altered), the major protocol version of the corresponding FIC chunk is updated.

Also, the FIC chunk header signals whether the data of a corresponding FIC chink payload carry mapping information between an ensemble and a mobile service within the current M/H frame, or whether the data of a corresponding FIC chink payload carry mapping information between an ensemble and a mobile service within the next M/H frame. Furthermore, the FIC chunk header also signals the number of transport stream IDs of a mobile service through which the current FIC chunk is being transmitted and the number of ensembles being transmitted through the corresponding mobile service.

Accordingly, for this, the FIC chunk header may include an FIC_major_protocol_version field, an FIC_minor_protocol_version field, an FIC_chunk_header_extension_length field, an ensemble_loop_header_extension_length field, an M/H_service_loop_extension_length field, a current_next_indicator field, a transport_stream_id field, and a num_ensembles field.

The FIC_major_protocol_version field corresponds to a 2-bit unsigned integer field that represents the major version level of an FIC chunk syntax. A change in the major version level shall indicate a change in a non-backward-compatible level. When the FIC_major_protocol_version field is updated, legacy (or conventional) receivers, which can process the prior major protocol version of an FIC chunk protocol, shall avoid processing the FIC chunk.

The FIC_minor_protocol_version field corresponds to a 3-bit unsigned integer field that represents the minor version level of an FIC chunk syntax. When it is assumed that the major version level remains the same, a change in the minor version level shall indicate a change in a backward-compatible level. More specifically, when the FIC_minor_protocol_version field is updated, legacy (or conventional) receivers, which can process the same major version of the FIC chunk protocol, may process a portion of the FIC chunk.

The FIC_Chunk_header_extension_length field corresponds to a 3-bit unsigned integer field identifying the length of FIC chunk header extension bytes, which are generated by the minor protocol version update of the corresponding FIC chunk. Herein, the extension bytes are appended (or added) at the end of the corresponding FIC chunk header.

The ensemble_header_extension_length field corresponds to a 3-bit unsigned integer field identifying the length of the ensemble header extension bytes, which are generated by the minor protocol version update of the corresponding FIC chunk. Herein, the extension bytes are appended (or added) at the end of the corresponding ensemble loop header.

Also, the M/H_service_loop_extension_length field corresponds to a 4-bit unsigned integer field identifying the length of the ensemble header extension bytes, which are generated by the minor protocol version update of the M/H service loop. Herein, the extension bytes are appended (or added) at the end of the corresponding M/H service loop.

For example, it is assumed that the FIC chunk includes 2 ensembles (i.e., ensemble 0 and ensemble 1). More specifically, it is assumed that two mobile services are transmitted through ensemble 0, and one mobile service is transmitted through ensemble 1. At this point, when the minor protocol version of the FIC chunk is changed, and the FIC chunk header is expanded by 1 byte, the FIC_chunk_header_extension_length field is marked as ‘001’. In this case, a 1-byte expansion field (i.e., FIC_Chunk_header_extension_bytes field) is added at the end of the FIC chunk header. Also, the legacy receiver skips the 1-byte expansion field, which is added at the end of the FIC chunk header, without processing the corresponding expansion field.

Additionally, when the ensemble loop header within the FIC chunk is expanded by 2 bytes, the ensemble_loop_header_extension_length field is marked as ‘010’. In this case, a 2-byte expansion field (i.e., Ensemble_loop_header_extension_bytes field) is respectively added at the end of the ensemble 0 loop header and at the end of the ensemble 1 loop header. Also, the legacy receiver skips the 2-byte expansion fields, which are respectively added at the end of the ensemble 0 loop header and at the end of the ensemble 1 loop header, without processing the corresponding 2-byte expansion fields.

Furthermore, when the mobile service loop of the FIC chunk is expanded by 1 byte, the M/H_service_loop_extension_length field is marked as ‘001’. In this case, a I-byte expansion field (i.e., M/H_service_loop_extension_bytes field) is respectively added at the end of 2 mobile service loops being transmitted through ensemble 0 loop and at the end of 1 mobile service loop being transmitted through the ensemble 1 loop. And, the legacy receiver skips the 1-byte expansion fields, which are respectively added at the end of 2 mobile service loops being transmitted through ensemble 0 loop and at the end of 1 mobile service loop being transmitted through the ensemble 1 loop, without processing the corresponding 1-byte expansion fields.

As described above, when the FIC_minor_protocol version field is changed, a legacy (or conventional) receiver (i.e., a receiver that cannot adopt the minor protocol version change in the corresponding FIC chunk) processes the fields apart from the extension field. Thereafter, the legacy receiver uses the FIC_chunk_header_extension_length field, the ensemble_loop_header_extension_length field, and the M/H_service loop_extension_length field, so as to skip the corresponding expansion fields without processing the corresponding fields. When using a receiving system that can adopt the corresponding minor protocol version change of the FIC chunk, each length field is used to process even the corresponding expansion field.

The current_next_indicator field corresponds to a 1-bit indicator, which, when set to ‘1’, indicates that the corresponding FIC chunk is currently applicable. Alternatively, when the current_next_indicator field is set to ‘0’, the current_next_indicator field indicates that the corresponding FIC chunk will be applicable for the next M/H frame. Herein, when the current_next_indicator field is set to ‘0’, the most recent version of the FIC chunk being transmitted with the current_next_indicator field set to ‘1’ shall be currently applicable. More specifically, when the current_next_indicator field value is set to ‘1’, this indicates that the corresponding FIC chunk transmits the signaling data of the current M/H frame. Further, when the current_next_indicator field value is set to ‘0’, this indicates that the corresponding FIC chunk transmits the signaling data of the next M/H frame. When reconfiguration occurs, wherein the mapping information between the ensemble within the current M/H frame and the mobile service differs from the ensemble within the next M/H frame and the mobile service, the M/H frame prior to reconfiguration is referred to as the current M/H frame, and the M/H frame following reconfiguration is referred to as the next M/H frame.

The transport_stream_id field corresponds to a 16-bit unsigned integer number field, which serves as a label for identifying the corresponding M/H broadcast. The value of the corresponding transport_stream_id field shall be equal to the value of the transport_stream_id field included in the program association table (PAT) within the MPEG-2 transport stream of a main ATSC broadcast.

The num_ensembles field corresponds to an 8-bit unsigned integer field, which indicates the number of M/H ensembles carried through the corresponding physical transmission channel.

FIG. 35 illustrates an exemplary syntax structure of an FIC chunk payload according to an embodiment of the present invention.

For each ensemble corresponding to the num_ensembles field value within the FIC chunk header of FIG. 34, the FIC chunk payload includes configuration information of each ensemble and information on mobile services being transmitted through each ensemble.

The FIC chunk payload consists of an ensemble loop and a mobile service loop below the ensemble loop. The FIC chunk payload enables the receiver to determine through which ensemble a requested (or desired) mobile service is being transmitted. (This process is performed via mapping between the ensemble_id field and the M/H_service_id field.) Thus, the receiver may receive RS frames belonging to the corresponding ensemble.

In order to do so, the ensemble loop of the FIC chunk payload may include an ensemble_id field, an ensemble_protocol_version field, an SLT_ensemble_indicator field, a GAT_ensemble_indicator field, an MH_service_signaling_channel_version field, and a num_M/H_services field, which are collectively repeated as many times as the num_ensembles field value. The mobile service loop may include an MH_service_id field, a multi_ensemble_service field, an MH_service_status field, and an SP_indicator field, which are collectively repeated as many times as the num_M/H_services field.

The ensemble_id field corresponds to an 8-bit unsigned integer field, which indicates a unique identifier of the corresponding ensemble. For example, the ensemble_id field may be assigned with values within the range ‘0x00’ to ‘0x7F’. The ensemble_id field group (or associate) the mobile services with the respective ensemble. Herein, it is preferable that the value of the ensemble_id field is derived from the parade_id field carried (or transmitted) through the TPC data. If the corresponding ensemble is transmitted through a primary RS frame, the most significant bit is set to ‘0’, and the remaining least significant bits are used as the parade_id field value of the corresponding parade. Meanwhile, if the corresponding ensemble is transmitted through a secondary RS frame, the most significant bit is set to ‘0’, and the remaining least significant bits are used as the parade_id field value of the corresponding parade.

The ensemble_protocol_version field corresponds to a 5-bit field, which specifies a version of the corresponding ensemble structure.

The SLT_ensemble_indicator field is a 1-bit field, which indicates whether or not the SLT is being transmitted to the service signaling channel of the corresponding ensemble. For example, when the SLT_ensemble_indicator field value is equal to ‘1’, this may indicate that the SLT is being transmitted to the service signaling channel. On the other hand, when the SLT_ensemble_indicator field value is equal to ‘0’, this may indicate that the SLT is not being transmitted.

The GAT_ensemble_indicator field is also a 1-bit field, which indicates whether or not the GAT is being transmitted to the service signaling channel of the corresponding ensemble. For example, when the GAT_ensemble_indicator field value is equal to ‘1’, this may indicate that the GAT is being transmitted to the service signaling channel. On the other hand, when the GAT_ensemble_indicator field value is equal to ‘0’, this may indicate that the GAT is not being transmitted.

The MH_service_signaling_channel_version field corresponds to a 5-bit field, which indicates a version number of the service signaling channel of the corresponding ensemble.

The num_M/H_services field corresponds to an 8-bit unsigned integer field, which represents the number of mobile (i.e., M/H) services carried through the corresponding M/H ensemble.

For example, when the minor protocol version within the FIC chunk header is changed, and when an extension field is added to the ensemble loop header, the corresponding extension field is added immediately after the num_M/H_services field. According to another embodiment of the present invention, if the num_M/H_services field is included in the mobile service loop, the corresponding extension field that is to be added in the ensemble loop header is added immediately after the M/H_service_configuration_version field.

The M/H_service_id field of the mobile service loop corresponds to a 16-bit unsigned integer number, which identifies the corresponding M/H service. The value (or number) of the M/H_service_id field shall be unique within the mobile (M/H) broadcast.

The multi_ensemble_service field is a 2-bit enumerated field, which indicates whether the corresponding mobile (M/H) service is transmitted through (or over) one ensemble, or whether the corresponding mobile (M/H) service is transmitted through (or over) multiple ensembles. Also, the value of the multi_ensemble_service field indicates whether or not the mobile service is valid (or rendered meaningfully) only for the mobile service portion being transmitted through (or over) the corresponding ensemble.

The M/H_service_status field corresponds to a 2-bit enumerated field, which identifies the status of the corresponding M/H service. For example, the most significant bit of the M/H_service_status field indicates whether the corresponding M/H service is active (when set to ‘1’) or inactive (when set to ‘0’). Furthermore, the least significant bit indicates whether the corresponding M/H service is hidden (when set to ‘1’) or not (when set to ‘0’).

The SP_indicator field corresponds to a 1-bit field, which, when set to ‘1’, indicates whether or not service protection is applied to at least one of the components required for providing a significant presentation of the corresponding M/H service.

For example, when the minor protocol version of the FIC chunk is change, and if an expansion field is added to the mobile service loop, the expansion field is added after the SP_indicator field.

Also, the FIC chunk payload may include an FIC_chunk_stuffing( ) field. Stuffing of the FIC_chunk_stuffing( ) field may exist in an FTC-Chunk, to keep the boundary of the FIC-Chunk to be aligned with the boundary of the last FTC-Segment among FIC segments belonging to the FIC chunk. The length of the stuffing is determined by how much space is left after parsing through the entire FIC-Chunk payload preceding the stuffing.

At this point, the transmitting system (not shown) according to the present invention divides the FIC chunk into multiple FIC segment payloads and forms a plurality of FIC segments by adding each FIC segment header to each FIC segment payload, thereby outputting the FIC segments to the receiving system in FIC segment units. The size of each FIC segment unit is 37 bytes, and each FIC segment consists of a 2-byte FIC segment header and a 35-byte FIC segment payload. More specifically, an FIC chunk, which is configured of an FIC chunk header and an FIC chunk payload, is segmented by units of 35 bytes. Also, an FTC segment is configured by adding a 2-byte FIC segment header in front of each segmented 35-byte unit.

According to an embodiment of the present invention, the length of the FIC chunk payload is variable. Herein, the length of the FIC chunk varies depending upon the number of ensembles being transmitted through the corresponding physical transmission channel and the number of mobile services included in each ensemble.

Also, the FIC chunk payload may include stuffing data. In this case, the stuffing data are used for the boundary alignment of the FIC chunk and the last FIC-Segment, among FIC segments belonging to the FIC chunk, according to the embodiment of the present invention. Accordingly, by minimizing the length of the stuffing data, unnecessary wasting of FIC segments can be reduced.

At this point, the number of stuffing data bytes being inserted in the FIC chunk can be calculated by using Equation 6 below.

The number of stuffing data bytes=35−j

j=(5÷the number of signaling data bytes being inserted in the FIC chunk payload) mod 35  Equation 6

For example, when the added total length of the 5-byte header within the FIC chunk and signaling data, which is to be inserted in the payload within the FIC chunk, is equal to 205 bytes, the payload of the FIC chunk may include 5 bytes of stuffing data because j is equal to 30 in Equation 6. Also, the length of the FIC chunk payload including the stuffing data is equal to 210 bytes. Thereafter, the FIC chunk is divided into 6 FIC segments, which are then transmitted. At this point, a segment number is sequentially assigned to each of the 6 FIC segments divided from the FIC chunk.

Furthermore, the present invention may transmit the FIC segments divided from a single FIC chunk to a single sub-frame, or may transmit the divided FIC segments to multiple sub-frames. If the FIC chunk is divided and transmitted to multiple sub-frames, signaling data, which are required even when the amount of data that are to be transmitted through the FIC chunk is larger than the amount of FIC segments being transmitted through a single sub-frame (this case corresponds to when multiple services having very low bit rates are being executed), may all be transmitted through the FIC chunk.

Herein, the FIC segment numbers represent FIC segment numbers within each FIC chunk, and not the FIC segment number within each sub-frame. Thus, the subordinate relation between the FIC chunk and the sub-frame can be eliminated, thereby reducing excessive waste of FIC segments.

Furthermore, the present invention may add a null FIC segment. Despite the repeated transmission of the FTC chunk, and when stuffing is required in the corresponding M/H frame, the null FIC segment is used for the purpose of processing the remaining FIC segments. For example, it is assumed that TNoG is equal to ‘3’ and that the FIC chunk is divided into 2 FIC segments. Herein, when the FIC chunk is repeatedly transmitted through 5 sub-frames within a single M/H frame, only 2 FIC segments are transmitted through one of the 5 sub-frames (e.g., the sub-frame chronologically placed in the last order). In this case, one null FIC segment is assigned to the corresponding sub-frame, thereby being transmitted. More specifically, the null FIC segment is used for aligning the boundary of the FIC chunk and the boundary of the M/H frame. At this point, since the null FIC segment is not an FIC segment divided from the FIC chunk, an FIC segment number is not assigned to the null FIC segment.

In the present invention, when a single FIC chunk is divided into a plurality of FIC segments, and when the divided FIC segments are included in each data group of at least one sub-frame within the M/H frame, so as to be transmitted, the corresponding FIC segments are allocated in a reversed order starting from the last sub-frame within the corresponding M/H frame. According to an embodiment of the present invention, in case a null FIC segment exists, the null FIC segment is positioned in the sub-frame within the M/H frame, so that the corresponding null FIC segment can be transmitted as the last (or final) segment.

At this point, in order to enable the receiving system to discard the null FIC segment without having to process the corresponding null FIC segment, identification information that can identify (or distinguish) the null FIC segment is required.

According to an embodiment of the present invention, the present invention uses the FIC_segment_type field within the header of the null FIC segment as the identification information for identifying the null FIC segment. In this embodiment, the value of the FIC_segment_type field within the null FIC segment header is set to ‘11’, so as to identify the corresponding null FIC segment. More specifically, when the FIC_segment_type field value within the null FIC segment header is set to ‘11’ and transmitted to the receiving system, the receiving system may discard the payload of the FIC segment having the FIC_segment_type field value set to ‘11’ without having to process the corresponding FIC segment payload. Herein, the value ‘11’ is merely an exemplary value given to facilitate and simplify the understanding of the present invention. As long as a pre-arrangement between the receiving system and the transmitting system is established, any value that can identify the null FIC segment may be given to the FIC_segment_type field. Therefore, the present invention will not be limited only to the example set presented herein. Furthermore, the identification information that can identify the null FIC segment may also be indicated by using another field within the FIC segment header.

FIG. 36 illustrates an exemplary syntax structure of an FIC segment header according to an embodiment of the present invention.

Herein, the FIC segment header may include an FIC_segment_type field, an FIC_chunk_major_protocol_version field, a current_next_indicator field, an error_indicator field, an FIC_segment_num field, and an FIC_last_segment_num field. Each field will now be described as follows.

The FIC_segment_type field corresponds to a 2-bit field, which, when set to ‘00’ indicates that the corresponding FIC segment is carrying a portion of an FIC chunk. Alternatively, when the FIC_segment_type field is set to ‘11’, the FIC_segment_type field indicates that the corresponding FIC segment is a null FIC segment, which transmits stuffing data. Herein, the remaining values are reserved for future use.

The FIC_Chunk_major_protocol_version field corresponds to a 2-bit field, which indicates a major protocol version of the corresponding FIC chunk. At this point, the value of the FIC_Chunk_major_protocol_version field should be the same as the value of the FIC_major_protocol_version field within the corresponding FIC chunk header. Since reference may be made to the description of the FIC chunk header shown in FIG. 34, a detailed description of the major protocol version of the FIC chunk syntax will be omitted for simplicity.

The current_next_indicator field corresponds to a 1-bit indicator, which, when set to ‘1’, shall indicate that the corresponding FIC segment is carrying a portion of the FIC chunk, which is applicable to the current M/H frame. Alternatively, when the value of the current_next_indicator field is set to ‘0’, the current_next_indicator field shall indicate that the corresponding FIC segment is carrying a portion of the FIC chunk, which will be applicable for the next M/H frame.

The error_indicator field corresponds to a 1-bit field, which indicates whether or not an error has occurred in the corresponding FIC segment during transmission. Herein, the error_indicator field is set to ‘1’, when an error has occurred. And, the error_indicator field is set to ‘0’, when an error does not exist (or has not occurred). More specifically, during the process of configuring the FIC segment, when a non-recovered error exists, the error_indicator field is set to ‘1’. More specifically, the error_indicator field enables the receiving system to recognize the existence (or presence) of an error within the corresponding FIC segment.

The FIC_segment_num field corresponds to a 4-bit unsigned integer number field, which indicates a number of the corresponding FIC segment. For example, if the corresponding FIC segment is the first FIC segment of the FIC chunk, the value of the FIC_segment_num field shall be set to ‘0x0’. Also, if the corresponding FIC segment is the second FIC segment of the FIC chunk, the value of the FIC_segment_num field shall be set to ‘0x1’. More specifically, the FIC_segment_num field shall be incremented by one with each additional FIC segment in the FIC chunk. Herein, if the FIC chunk is divided into 4 FIC segments, the FIC_segment_num field value of the last FIC segment within the FIC chunk will be indicated as ‘0x3’.

The FIC_last_segment_num field corresponds to a 4-bit unsigned integer number field, which indicates the number of the last FIC segment (i.e., the FIC segment having the highest FIC_segment_num field value) within a complete FIC chunk.

In the conventional method, FIC segment numbers are sequentially assigned (or allocated) for each FIC segment within one sub-frame. Therefore, in this case, the last FIC segment number always matches with the TNoG (i.e., the last FIC segment number is always equal to the TNoG). However, when using the FIC number assignment method according to the present invention, the last FIC segment number may not always match with the TNoG. More specifically, the last FIC segment number may match with the TNoG, or the last FIC segment number may not match with the TNoG. The TNoG represents a total number of data groups that are allocated (or assigned) to a single sub-frame. For example, when the TNoG is equal to ‘6’, and when the FIC chunk is divided into 8 FIC segments, the TNoG is equal to ‘6’, and the last FIC segment number is ‘8’.

According to another embodiment of the present invention, the null FIC segment may be identified by using the value of the FIC_segment_num field within the FIC segment header. More specifically, since an FIC segment number is not assigned to the null FIC segment, the transmitting system allocates null data to the FIC_segment_num field value of the null FIC segment, and the receiving system may allow the FIC segment having null data assigned to the FIC_segment_num field value to be recognized as the null FIC segment. Herein, instead of the null data, data pre-arranged by the receiving system and the transmitting system may be assigned to the FIC_segment_num field value, instead of the null data.

As described above, the FIC chunk is divided into a plurality of FIC segments, thereby being transmitted through a single sub-frame or being transmitted through multiple sub-frames. Also, FIC segments divided from a single FIC chunk may be transmitted through a single sub-frame, or FIC segments divided from multiple single FIC chunks may be transmitted through a single sub-frame. At this point, the number assigned to each FIC segment corresponds to a number within the corresponding FIC chunk (i.e., the FIC_seg_number value), and not the number within the corresponding sub-frame. Also, the null FIC segment may be transmitted for aligning the boundary of the M/H frame and the boundary of the FIC chunk. At this point, an FIC segment number is not assigned to the null FIC segment.

As described above, one FIC chunk may be transmitted through multiple sub-frames, or multiple FIC chunks may be transmitted through a single sub-frame. However, according to the embodiment of the present invention, the FIC segments are interleaved and transmitted in sub-frame units.

Meanwhile, FIG. 37 illustrates an exemplary structure of a bit stream syntax of an SMT section which is included in the RS frame and then transmitted. Herein, the SMT section is configured in an MPEG-2 private section format for simplicity. However, the SMT section data may be configured in any possible format.

The SMT may provide access information of mobile services within an ensemble including the SMT. Also, the SMT may provide information required for the rendering of mobile services. Furthermore, the SMT may include at least one or more descriptors. Herein, other additional (or supplementary) information may be described by the descriptor.

At this point, the service signaling channel that transmits the SMT may further include another signaling table (e.g., GAT) in addition to the SMT.

Herein, according to the embodiment of the present invention, IP datagrams of the service signaling channel have the same well-known destination IP address and the same well-known destination UDP port number. Therefore, the SMT included in the service signaling data is distinguished (or identified) by a table identifier. More specifically, the table identifier may correspond to a table_id existing in the corresponding table or in a header of the corresponding table section. And, when required, the table identifier may further refer to a table_id_extension field, so as to perform the identification process. Exemplary fields that can be transmitted through the SMT section will now be described in detail.

A table_id field is an 8-bit table identifier, which may be set up as an identifier for identifying the SMT.

A section_syntax_indicator field corresponds to an indicator defining the section format of the SMT. For example, the section_syntax_indicator field shall be set to ‘0’ to always indicate that this table is derived from the “short” form of the MPEG-2 private section table format may correspond to MPEG long-form syntax.

A private_indicator field is a 1-bit field, which indicates whether or not the SMT follows (or is in accordance with) a private section.

A section_length field is a 12-bit field, which specifies the section length of the remaining SMT data bytes immediately following the section_length field.

A table_id_extension field corresponds to a table-dependent 16-bit field. Herein, the table_id_extension field corresponds to a logical portion of the table_id field providing the scope for the remaining fields. The table_id_extension field includes a SMT_protocol_version field and an ensemble_id field.

The SMT_protocol_version field corresponds to an 8-bit unsigned integer field. Herein, the SMT_protocol_version field indicates a protocol version for allowing the corresponding SMT to carry, in a future process, parameters that may be structure differently from those defined in the current protocol. Presently, the value of the SMT_protocol_version field shall be equal to zero (0). Non-zero values of the SMT_protocol_version field may be used by a future version of this standard to indicate structurally different tables.

The ensemble_id field corresponds to an 8-bit field. Herein, the ID values associated with the corresponding ensemble that can be assigned to the ensemble_id field may range from ‘0x00’ and ‘0x3F’. It is preferable that the value of the ensemble_id field is derived from the TPC data of the parade_id field. When the corresponding ensemble is transmitted through a primary RS frame, the most significant bit (MSB) is set to ‘0’, and the remaining 7 bits are used as the parade_id field value of the corresponding parade. Meanwhile, when the corresponding ensemble is transmitted through a primary RS frame, the most significant bit (MSB) is set to ‘1’, and the remaining 7 bits are used as the parade_id field value of the corresponding parade.

A version_number field corresponds to a 5-bit field, which specifies the version number of the SMT.

A current_next_indicator field corresponds to a 1-bit field indicating whether or not the SMT section is currently applicable.

A section_number field is an 8-bit field specifying the number of the current SMT section.

A last_section_number field corresponds to an 8-bit field that specifies the number of the last section configuring the corresponding SMT.

And, a num_MH_services field corresponds to an 8-bit field, which specifies the number of mobile services in the corresponding SMT section.

Hereinafter, a number of ‘for’ loop (also referred to as mobile (M/H) service loop) statements equivalent to the number of mobile services corresponding to the num_MH_services field is performed so as to provide signaling information on multiple mobile services. More specifically, signaling information of the corresponding mobile service is indicated for each mobile service that is included in the SMT section. Herein, the following field information corresponding to each mobile service may be provided as described below.

An MH_service_id field corresponds to a 16-bit unsigned integer number, which can uniquely identify the corresponding mobile service within the scope of the corresponding SMT section.

A multi_ensemble_service field corresponds to a 2-bit field, which indicates whether the corresponding mobile service is transmitted through one or more ensembles. Since the multi_ensemble_service field has the same meaning as the multi_ensemble_service field included in the FIC chunk, detailed description of the same will be omitted for simplicity.

An MH_service_status field corresponds to a 2-bit field, which can identify the status of the corresponding mobile service. Herein, the MSB indicates whether the corresponding mobile service is active (‘1’) or whether the corresponding mobile service is inactive (‘0’). Also, the LSB indicates whether the corresponding mobile service is hidden (‘1’) or not hidden (‘0’).

An SP_indicator field corresponds to a 1-bit field, which specifies service protection status of the corresponding mobile service. If the SP_indicator field is set to ‘1’, then service protection is applied to at least one of the components needed to provide a meaningful presentation of the corresponding service.

A short_MH_service_name_length field corresponds to a 3-bit field, which indicates the length of a short service name described in a short_service_name field in byte-length units.

The short_MH_service_name field indicates the short name of the corresponding mobile service.

An MH_service_category field is a 6-bit field, which identifies the type category of the corresponding mobile service.

A num_components field corresponds to a 5-bit field, which specifies the number of IP stream components in the corresponding mobile service.

An IP_version_flag field corresponds to a 1-bit indicator, which when set to ‘0’ indicates that a source_IP_address field, an MH_service_destination_IP_address field, and a component_destination_IP_address field correspond to IPv4 addresses. The value of ‘1’ for the IP_version_flag field is reserved for any possible future indication that the source_IP_address field, the MH_service_destination_IP_address field, and the component_destination_IP_address field correspond to IPv6 addresses. However, the usage of IPv6 addressing is currently undefined.

A source_IP_address_flag corresponds to a 1-bit Boolean flag, which indicates, when set, that a source IP address value for the corresponding service exists (or is present) so as to indicate a source specific multicast.

An MH_service_destination IP_address_flag corresponds to a 1-bit, which indicates, when set, that the corresponding IP stream component is transmitted through an IP datagram having a destination IP address different from that of the MH_service_destination_IP_address field. Therefore, when the MH_service_destination_IP_address_flag is set, the receiving system may use the component_destination_IP_address as the destination_IP_address in order to access the corresponding IP stream component. Furthermore, the receiving system ignores (or disregards) the MH_service_destination_IP_address field within the mobile service loop.

The source_IP_address field corresponds to a 32-bit field or a 128-bit field. When the source_IP_address_flag is set to ‘1’, the source_IP_address field is required to be interpreted (or analyzed). However, when the source_IP_address_flag is set to ‘0’, the source_IP_address field is not required to be interpreted (or analyzed). When the source_IP_address_flag is set to ‘1’, and when the IP_version_flag field is set to ‘0’, the corresponding field indicates that the source_IP_address field indicates a 32-bit IPv4 address specifying the corresponding mobile service source. Alternatively, if the IP_version_flag field is set to ‘1’, the source_IP_address field indicates a 32-bit IPv6 address specifying the corresponding mobile service source.

The MH_service_destination_IP_address field corresponds to a 32-bit field or a 128-bit field. When the MH_service_destination_IP_address_flag field is set to ‘1’, the MH_service_destination IP_address_flag is required to be interpreted (or analyzed). However, when the MH_service_destination_IP_address_flag is set to ‘0’, the MH_service_destination_IP_address_flag is not required to be interpreted (or analyzed). Herein, if the MH_service_destination_IP_address_flag is set to ‘1’, and if the IP_version_flag field is set to ‘0’, the MH_service_destination_IP_address field indicates a 32-bit destination IPv4 address for the corresponding mobile service. Alternatively, if the MH_service_destination_IP_address_flag is set to ‘1’, and if the IP_version_flag field is set to ‘1’, the MH_service_destination_IP_address field indicates a 64-bit destination IPv6 address for the corresponding mobile service. In case the corresponding MH_service_destination_IP_address field cannot be interpreted, the component_destination_IP_address field within a component loop shall be interpreted. And, in this case, the receiving system shall use the component_destination_IP_address in order to access the IP stream component.

Meanwhile, the SMT according to the embodiment of the present invention provides information on multiple components using the ‘for’ loop statement.

Hereinafter, a number of ‘for’ loop (also referred to as component loop) statements equivalent to the number of components corresponding to the num_component field value is performed so as to provide access information on multiple components. More specifically, access information of each component included in the corresponding mobile service is provided. In this case, the following field information on each component may be provided as described below.

A component_source_IP_address_flag field is a 1-bit field (or a 1-bit Boolean flag), which indicates, when set to ‘1’, that the component_source_IP_address field is present for this component.

More specifically, a mobile service may include diverse types of components, for example, a mobile service may include an audio component, or a mobile service may include a video component, or a mobile service may include a FLUTE component.

At this point, when the component_source_IP_address_flag field is set to ‘1’, this signifies that the component_source_IP_address field exists, and this field indicates a source IP address of an IP datagram carrying the corresponding component.

For example, when the component_source_IP_address_flag field of the FLUTE component is set to ‘1’, the component_source_IP_address field indicates the source IP address of the IP datagram carrying the FLUTE component.

According to an embodiment of the present invention, in case a service_source_IP_address field within a mobile service loop and a component_source_IP_address within a component loop both exist, yet if the field values are different from one another, the source IP address of the IP datagram of the corresponding component is acquired from the component_source_IP_address field. More specifically, the service_source_IP_address field within the mobile service loop is disregarded.

According to another embodiment of the present invention, in case the service_source_IP_address field exists and the component_source_IP_address field does not exist, the source IP address of the IP datagram of the corresponding component is acquired from the service_source_IP_address field. And, in the opposite case, i.e., in case the service_source_IP_address field does not exists and the component_source_IP_address field exists, the source IP address of the IP datagram of the corresponding component is acquired from the component_source_IP_address field.

As described above, in the present invention, the component_source_IP_address field exists when the component_source_IP_address_flag field value is equal to ‘1’. And, according to an embodiment of the present invention, when the component_source_IP_address field exists, the source IP address of the IP datagram of the corresponding component is identical to the component_source_IP_address field value. And, according to another embodiment of the present invention, in case the component_source_IP_address field does not exist, the source IP address of the IP datagram of the corresponding component is identical to the service_source_IP_address field value.

And, according to another embodiment of the present invention, in case the service_source_IP_address field and the component_source_IP_address field do not exist, the source IP address is not used when acquiring the IP datagram of the corresponding component.

An essential_component_indicator field is a 1-bit field, which indicates that the corresponding component is an essential component for the mobile service, when the essential_component_indicator field value is set to ‘1’. Otherwise, the essential_component_indicator field indicates that the corresponding component is an optional component. For example, in case of a basic layer audio stream and video stream, the essential_component_indicator field value is set to ‘1’. And, in case of the enhanced layer video stream, the essential_component_indicator field value is set to ‘0’.

A component_destination_IP_address_flag field corresponds to a 1-bit Boolean flag. When the component_destination_IP_address_flag field is set to ‘1’, this indicates that a component_destination_IP_address exists for the corresponding component.

A port_num_count field corresponds to a 6-bit field, which indicates a UDP port number associated with the corresponding UDP/IP stream component. Herein, the destination UDP Port number value is increased by 1 starting from a destination_UDP_port_num field value. The destination_UDP_port_num field corresponds to a 16-bit field, which indicates a destination UDP port number for the corresponding IP stream component.

A component_source_IP_address field corresponds to a 32-bit or 128-bit field, which exists when the value of the component_source_IP_address_flag field is equal to ‘1’. At this point, in case the IP_version_flag field is set to ‘0’, the component_source_IP_address field indicates a 32-bit source IPv4 address for the corresponding IP stream component. Also, in case the IP_version_flag field is set to ‘1’, the component_source_IP_address field indicates a 128-bit source IPv6 address for the corresponding IP stream component.

According to an embodiment of the present invention, in case the component_source_IP_address field exists, the source IP address of an IP datagram of the corresponding component is acquired from the component_source_IP_address field.

A component_destination_IP_address field corresponds to a 32-bit field or a 128-bit field. When the IP_version_flag field is set to ‘0’, the component_destination_IP_address field indicates a 32-bit destination IPv4 address for the corresponding IP stream component.

Furthermore, when the IP_version_flag field is set to ‘1’, the component_destination_IP_address field indicates a 128-bit destination IPv6 address for the corresponding IP stream component. When this field is present, the destination address of the IP datagrams carrying the corresponding component of the M/H service shall match the address in the component_destination_IP_address field. Alternatively, when this field is not present, the destination address of the IP datagrams carrying the corresponding component shall match the address in the M/H_service_destination_IP_address field. The conditional use of the 128 bit-long address version of this field is to facilitate possible future usage of the IPv6, although the usage of the IPv6 is currently undefined.

A num_component_level descriptors field corresponds to a 4-bit field, indicating a number of descriptors providing additional information on the component level.

A number of component_level_descriptor( ) corresponding to the value of the num_component_level_descriptors field is included in the component loop, so as to provide additional (or supplemental) information on the corresponding component.

A num_MH_service_level_descriptors field corresponds to a 4-bit field indicating a number of descriptors providing additional information of the corresponding mobile service level.

A number of service_level_descriptor( ) corresponding to the value of the num_MH_service_level_descriptors field is included in the mobile service loop, so as to provide additional (or supplemental) information on the mobile service.

A num_ensemble_level descriptors field corresponds to a 4-bit field, which indicates a number of descriptors providing additional information on ensemble levels.

Furthermore, a number of ensemble_level_descriptor( ) corresponding to the value of the num_ensemble_level_descriptors field is included in the ensemble loop, so as to provide additional (or supplemental) information on the ensemble.

FIG. 38 illustrates an embodiment of a bit stream syntax structure of a component_level_descriptors( ). The component_descriptor( ) is used as one of the component level descriptor component_level_descriptors( ) of the NST and describes additional signaling information of the corresponding component.

The following is a description of each field of the component_descriptor( ).

In FIG. 38, a descriptor_tag field (8-bit) is a descriptor identifier and it can be set as an identifier that identifies the component_descriptor( ).

A descriptor_length field (8-bit) describes the remaining length of the descriptor starting after the descriptor_length field and to the end of this descriptor, in bytes.

A component_type field (7-bit) shall identify the encoding format of the component. The value may be any of the values assigned by IANA for the payload_type of an RTP/AVP stream, or it may be any of the values assigned by ATSC, or it may be a “dynamic value” in the range 96-127. For components consisting of media carried via RTP, the value of this field shall match the value in the payload_type field in the RTP header of the IP stream carrying this component. Note that additional values of the component_type field in the range of 43-71 can be defined in future versions of this standard.

A component_encryption_flag (1-bit) informs whether the corresponding component is encrypted or not.

A Num_STKM_streams field (8-bit) indicates the number STKM streams if component_encryption_flag has been encrypted. (The num_STKM_streams field (8-bit) is an 8-bit unsigned integer field that shall identify the number of STKM streams associated with this component.

A STKM_stream_id field (8-bit) is repeated as much as the field value of Num_STKM_streams and indicates a value that identifies a SKTM stream that can acquire a key required for decryption.

A component_data (component_type) element provides the encoding parameters and/or other parameters necessary for rendering this component. The structure of the component_data is determined by the value of component_type field.

For example, if the component_type field value is 35 then component_data (component_type) field provides component data for H.264/AVC video stream.

In another example, if the component_type field value is 38 then component_data (component_type) field provides data for FLUTE file delivery.

One mobile service can be included in multiple FLUTE sessions. Thus, one mobile service may be configured with plurality of FLUTE sessions. Each FLUTE session may be signaled using component_data( ).

Meanwhile, according to another embodiment of the present invention, a broadcast receiver to provide a user with a mobile broadcast service by processing a mobile broadcast signal provided over a mobile broadcast network, particularly the M/H broadcast network is allowed to provide disaster broadcasting (or disaster alert). To provide the disaster broadcast containing disaster information, signaling information for the disaster broadcast is necessary. Hereinafter, a description will be given of various examples of a method for signaling the signaling information for the disaster broadcast.

The signaling information may be signaled to the FIC chunk and/or the SMT. At this time, the signaling information signaled to the FIC chunk and the signaling information signaled to the SMT may be different from, or identical to each other, or parts thereof may duplicate.

In addition, the present invention defines a new table. The signaling information for disaster broadcast may be signaled to this table. This table will be referred to as an Emergency Alert Table (EAT).

Hereinafter, a description will be given of signaling information for the disaster broadcast using an FIC chunk. The disaster broadcast may be a specific channel or a text indicating the disaster status. In this embodiment, a message containing text-type disaster information for informing the disaster status is referred to as an emergency alert message for simplicity of description.

As an example, the signaling information signaled to the FIC chunk contains at least one of emergency alert system (EAS) indication information (or referred to as an EAS indicator field) for informing the current mobile broadcast of existence of an emergency alert message and wake-up indication information (or referred to as a wake-up indicator field) for supporting a wake-up function.

The EAS indication information informs of existence of an emergency alert message in the current mobile broadcast.

The wake-up indication information informs of whether the emergency alert message needs the wake-up function. That is, the wake-up indication information is needed to support the wake-up function of the broadcast receiver in issuing a disaster alert.

Herein, the wake-up function refers to a function for compulsorily switching the broadcast receiver to the active mode broadcast receiver even if the broadcast receiver is in the sleep mode (or referred to as the standby mode when a serious emergency alert message requiring switch to the active mode is issued. To support the wake-up function, the broadcast receiver needs to consistently watch broadcast signals even in the sleep mode and to recognize how urgent the disaster alert is as quickly as possible.

The FIC chunk is configured with an FIC chunk header and an FIC chunk payload, and the FIC chunk is divided into a plurality of FIC segment payloads. When the FIC segment header is added to each of the FIC segment payloads, one FIC segment is constructed. The FIC segment is transmitted through one data group. That is, the FIC segment is the smallest unit of transmission at the physical layer.

FIG. 39 illustrates another embodiment of the syntax structure of the FIC segment header to which the EAS indication information and the wake-up indication information are signaled. Details of the FIC segment header of FIG. 39 are the same as those of the FIC segment header of FIG. 36 except that the FIC segment header of FIG. 39 allocates the wake-up indicator field and the EAS indicator field using the two reserved bits of FIG. 36. Accordingly, a description of the fields of FIG. 39 identical to those of FIG. 36 will be omitted.

In FIG. 39, the wake-up indicator field has, for example, 1 bit allocated thereto, and indicates wake-up. The broadcast receiver determines whether to switch to the active mode according to the value of the wake-up indicator field.

In addition, the EAS indicator field has, for example, 1 bit allocated thereto, and indicates existence of an emergency alert message in the current mobile broadcast.

By adding the EAS indicator field to the FIC segment header as described above, the broadcast receiver may quickly sense whether an emergency alert message is included in the current broadcast service.

FIG. 40 illustrates another embodiment of the syntax structure of the FIC segment header to which the EAS indication information and the wake-up indication information are signaled. Details of the FIC segment header of FIG. 40 are the same as those of the FIC segment header of FIG. 36 except that the FIC segment header of FIG. 40 allocates the wake-up indicator field using the two reserved bits of FIG. 36. Accordingly, a description of the fields of FIG. 39 identical to those of FIG. 36 will be omitted.

That is, in FIG. 40, the wake-up indicator field has, for example, 2 bits allocated thereto, and indicates wake-up. The broadcast receiver determines whether to switch to the active mode according to the value of the wake-up indicator field when an emergency alert message is issued.

FIG. 41 shows an example of meanings allocated to the values of the 2 bit wake-up indicator field. For example, when the value of the wake-up indicator field is 01, the wake-up function may be enabled. When 10, the wake-up function may be disabled. For example, when the value of the wake-up indicator field is 01, and the current mode is the sleep mode, the broadcast receiver switches to the active mode.

The opposite case is also possible. That is, when the value of the wake-up indicator field is 01, the wake-up function may be disabled. When 10, the wake-up function may be enabled. In the case that 1 bit is allocated to the wake-up indicator field, the wake-up function may be turned on/off using the 1 bit. Since this is an item selected by the designer, embodiments of the present invention are not limited to the above example.

While the wake-up indicator of FIG. 39 is provided with 1 bit allocated thereto, the wake-up indicator of FIG. 40 has 2 bits allocated to indicate wake-up.

In the case that the wake-up indicator field is allocated as shown in FIG. 40, the EAS indication information is allocated, for example, using the reserved bits of the FIC chunk payload.

FIG. 42 illustrates an embodiment of the syntax structure of the FIC chunk payload to which the EAS indication information is signaled. Details of the FIC chunk payload of FIG. 42 are the same as those of the FIC chunk payload of FIG. 35 except that the EAS indicator field is allocated using the reserved bit. Accordingly, a description of the fields of FIG. 42 identical to those of FIG. 35 will be omitted.

That is, in FIG. 42, 1 bit is allocated to the ensemble loop for the EAS indicator field (EAS_ensemble_indicator). This field indicates existence of an emergency alert message in the current broadcast.

For example, when the value of the EAS indicator field is 1, an ensemble identified by the ensemble identifier in the ensemble loop may be set to indicate that an emergency alert message has been received. The opposite case is also possible. That is, when the value of the EAS indicator field is 0, the ensemble may be set to indicate that the emergency alert message has been received. Since this is an item selected by the designer, embodiments of the present invention are not limited to the above example.

In performing wake-up, the broadcast receiver needs to specify an ensemble frequency (or a base band) at which an emergency alert message can be received. To this end, the EAS indicator field is needed.

That is, informing existence of an emergency alert message using the FIC segment header is the most efficient method for the wake-up function and quick acquisition of an emergency alert message in the broadcast receiver. However, if the FIC segment is the basic unit for creation of an FIC chunk, and the broadcast receiver does not respond to the change of reserved bits of the FIC segment header, existence of an emergency alert message in the current mobile broadcast cannot be recognized once the FIC chunks are collected. Accordingly, in this embodiment, by allocating the EAS indicator field to the FIC chunk payload, the broadcast receiver is allowed to notice whether an emergency alert message exists in the current ensemble immediately after the FIC chunks are collected.

In addition, in the case that the broadcast receiver is not in the active mode, the broadcast receiver is allowed to receive an emergency alert message with the minimum energy maintained by signaling wake-up information to the TPC of the smallest unit for signaling.

The wake-up information includes, for example, wake-up indication information. The wake-up information may further include wake-up version information.

For example, 1 bit of the wake-up indication information and 5 bits of the wake-up version information are signaled using the reserved bits in the syntax of the TPC data of FIG. 31.

Since the wake-up indication information (wake_up_indicator) has been described in detail in the description of the FIC, a detailed description thereof will be omitted. For example, if the value of the wake_up_indicator field is 0, and the broadcast receiver is in the sleep mode (or standby mode), the broadcast receiver is compulsorily switched to the active mode. If the value of the field is 1, the broadcast receiver maintains the current mode. That is, in the sleep mode, the receiver is allowed to continue monitoring the TPC. In the case that the receiver is providing the mobile broadcast service, it is allowed to keep providing the mobile broadcast service.

The wake-up version information (wake_up_version_number) indicates the version number of wake-up signaling. The receiver may compare the wake-up version numbers to determine whether the information is new wake-up information before switching from the sleep mode to the active mode to receive the FIC.

By signaling the wake-up information to the TPC data, the broadcast receiver is allowed to determine whether to perform the wake-up function based on the TPC data, namely, whether to compulsorily switch from the current mode to the active mode. In addition, by signaling the wake-up information to the TPC data, the broadcast receiver is allowed to compulsorily perform the wake-up function to receive disaster alert over mobile broadcast even when failing to receive signaling information related to the disaster alert. Particularly, by signaling the wake-up information to the TPC data, the broadcast receiver is allowed to receive disaster information with the minimum consumption of the battery even in a mode other than the active mode.

Meanwhile, an emergency alert message containing disaster information (or content) may be transmitted in various forms. For example, the emergency alert message may be transmitted in the form of a CAP message or syntax.

Herein, the common alerting protocol (CAP) message is an emergency alert message of a common format created by authoring authorities for generation of a disaster alert. A CAP message generated as above is delivered to various disaster systems including a commercial mobile alert system (CMAS) over the Open Platform for Emergency Networks (OPEN), which is an integrated network for delivery of emergency alert messages. Each disaster alert system processes a CAP message for its own purpose and use, thereby providing a corresponding disaster alert service. For example, the CMAS selects a message proper for a provider network among delivered emergency messages and extracts a text in 90 words or less from the message, thereby providing a disaster service in the form of a text message.

In an embodiment, the CAP message is carried in a descriptor and the descriptor is included in the SMT. The descriptor containing the CAP message will be referred to as an EAS message descriptor (EAS_Message_descriptor( )). When the EAS descriptor is transmitted, it may be contained in the ensemble level or the service level of the SMT.

FIG. 43 illustrates the syntax structure of the EAS message descriptor according to one embodiment of the present invention.

In FIG. 43, the descriptor_tag field (8 bits) is a descriptor identifier. An identifier (or a tag value) to identify whether a descriptor is the EAS message descriptor is allocated.

The descriptor_length field (8 bits) indicates the remaining length of this descriptor from the descriptor_length field to the end of the descriptor in unit of byte.

The Length_of_CAP field (8 bits) indicates the length of a CAP message transmitted in the multiple string structure.

The CAP message in the multiple string structure is transmitted by repeating the CAP field by the value of the Length_of_CAP field. At this time, a separate EAS syntax may be transmitted in place of the CAP message.

FIG. 44 illustrates the syntax structure of the EAS message descriptor according to another embodiment of the present invention.

In FIG. 44, the descriptor_tag field (8 bits) is a descriptor identifier, and an identifier (or a tag value) to identify whether a descriptor is the EAS message descriptor is allocated to this field.

The descriptor_length field (8 bits) indicates the remaining length of this descriptor from the descriptor_length field to the end of the descriptor in the unit of byte.

The CAP_version_number field (4 bits) indicates the version information of a CAP message. For example, when the CAP message changes, the value of the CAP_version_number field increases. Accordingly, the broadcast receiver is allowed to determine whether the CAP messages are repeated using this field value. That is, since the CAP message is emergency information, the same content may be periodically transmitted. In this case, every time a CAP message is received, the broadcast receiver can determine whether the received message is a change of the previously received message or new information, using the value of the CAP_version_number field.

The EAS_NRT_included_flag field (1 bit) indicates whether a non-real time (NRT) service related to a current disaster broadcast service (or emergency alert message) exists.

If the EAS_NRT_included_flag field indicates existence of an NRT service related to the current disaster broadcast, an EAS NRT loop including the essential_content_linkage field and num_associated_service field exists.

The essential_content_linkage field (8 bits) indicates the value of linkage between a file (or a content item) sent in NRT and the content (or a content item) in the ESG. For example, if the value of the essential_content_linkage field is 0, the user interface (UI) displays a list of NRT services for the EAS. If the value is not 0, the UE displays a file having the value of the essential_content_linkage field as the value of content_linkage on the screen. This means that the content contained in the file provided in NRT is highly associated with a disaster broadcast (or emergency alert message).

The num_associated_service field (4 bits) indicates the number of services associated with the current disaster broadcast and transmitted in NRT. An identifier of each of the associated services is indicated by repeating the associated_service_id field (16 bit) by the value of the num_associated_service field.

The CAP_message_type field (1 bit) indicates whether an emergency alert message is transmitted in the CAP message structure on syntax structure.

The length_of_CAP_message_id field (7 bits) indicates the length of the text of the CAP message identifier (ID).

The CAP_message_id field (variable) indicates the CAP message identifier in a text.

The length_of_CAP field (16 bit) indicates the length of the CAP message.

The CAP field (variable) contains a CAP message or EAS syntax.

Since the same content of the EAS message descriptor shown in FIG. 43 or 44 should be broadcasted in all broadcasts, and therefore the EAS message descriptor may be included in at least one of the ensemble level and service level of the SMT. The SMT is essentially included in all ensembles of a channel. That is, the EAS message descriptor may be transmitted as the ensemble level descriptor of the SMT, or as the service level descriptor. FIG. 45 illustrates an example of transmission of the EAS message descriptor included in the ensemble level, and FIG. 46 illustrates an example of transmission of the EAS message descriptor included in the service level.

In the case that the EAS message descriptor is transmitted through the ensemble level descriptor as shown in FIG. 45, the content contained in the EAS message descriptor is applied to all services (e.g., TV service #1 and TV service #2) of a corresponding ensemble (e.g., ensemble #1) in the same manner. If the EAS message descriptor is contained in the ensemble level and transmitted, the necessity of sending the EAS message descriptor for each of the services of the SMT is eliminated. Accordingly, the size of the SMT may be reduced. When the EAS message descriptor is transmitted as the ensemble level descriptor, the value of EAS_NRT_included_flag field shown in FIG. 44 may be set to 0. In this case, NRT associated information (i.e., disaster-related additional information) cannot be transmitted except the CAP message.

In the case that the EAS message descriptor is transmitted as the service level descriptor as shown in FIG. 46, the same content of the EAS message descriptor is contained in each service of the SMT. This may increase the size of the SMT compared to the case of transmission of the descriptor as the ensemble level descriptor, but can advantageously allow transmission of the NRT service-associated information to express additional information associated with the emergency alert message (i.e., disaster-related additional information) since all the descriptors of the SMT used in NRT are in the service level.

When the EAS message descriptor is transmitted as the service level descriptor, the value of the EAS_NRT_included_flag field shown in FIG. 44 may be set to one of 0 and 1. If the value of the EAS_NRT_included_flag field is 0, it indicates that there is no disaster-related additional information which is transmitted in NRT. If the value is 1, it indicates that there is disaster-related additional information which is transmitted in NRT.

The broadcast receiver extracts the EAS message descriptor by parsing the received SMT included in the ensemble, processes the CAP message contained in the EAS message descriptor, and then displays disaster information in the form of a text at the lower end 601 of the screen as shown in FIG. 47. Herein, the EAS message descriptor may be included in the ensemble level of the SMT or in the service level. In addition, while the disaster information in the form of a text is illustrated as being displayed at the lower end of the screen, it may be displayed at another portion of the screen, for example, one of the upper end, left side and right side. In addition, the disaster information in the form of a text may be scrolled from one side to the other.

As described above, the disaster-related additional information broadcast according to embodiments of the present invention may be transmitted in NRT. Herein, the disaster-related additional information includes various types of information such as image, video, and text, which may be greatly useful for the user when disaster happens.

FIG. 48 illustrates displaying the received disaster information in the form of a text contained in the EAS message descriptor at the lower end 601 of the screen and displaying the disaster-related additional information received in NRT in the form of an image or text at other portions 602 to 604 of the screen at the same time. The screen shown in FIG. 48 is simply an example. The screen size and the disposition of the disaster-related additional information may vary depending on the types and the number of pieces of the disaster-related additional information.

In one embodiment, the disaster-related additional information may be configured in one file and transmitted in NRT.

In mobile broadcast, the real time (RT) service literally refers to a service provided in real time. That is, this service is a time-dependent service. On the other hand, the NRT service refers to a service provided in non-real time compared to the RT service. That is, the non-real time service is not time-dependent. For example, a broadcasting station may transmit an RT service and provide an NRT service using a remaining bandwidth or a dedicated bandwidth. That is, the RT service and the NRT service are transmitted over the same channel or different channels.

In another example, the broadcast receiver according is capable of receiving a non-real time (NRT) service through media such as terrestrial broadcast, cable, and the Internet.

The NRT service is stored in the storage medium of the broadcast receiver, and is then displayed on a display device at a predetermined time or according to a request from the user. The NRT service may be stored in the form of a file in the storage. In one embodiment, the storage medium may be a built-in HDD mounted in the broadcast receiver. In another embodiment, the storage medium may be an external HDD or a universal serial bus (USB) memory connected to the exterior of a broadcast receiving system.

In one embodiment, one NRT service includes at least one content item (or referred to as content or NRT content), and one content item includes at least one file. In this present invention, the ‘file’ has the same meaning as the term ‘object’. A content item is the smallest unit that can be independently reproduced. For example, assume that news is provided in non-real time and that the new includes news on the economy, politics and life. In this case, the news may be viewed as the NRT service, and each of the news on the economy, politics, and life may be viewed as a content item, each of the news on the economy, politics, and life is configured in at least one files.

Content items/packets configuring an NRT service at the transmitter side such as a broadcasting station are packetized according to the file transfer protocol, and then packetized according to the asynchronous layered coding/layered coding transport (ALC/LCT) scheme. The packetized ALC/LCT data is then packetized according to the UDP, and the packetized ALC/LCT/UDP data is in turn packetized according to the IP scheme to form ALC/LCT/UDP/IP data. The packetized ALC/LCT/UDP/IP data will be referred to as IP datagram for simplicity of the description of the present invention. The OMA BCAST service guide information may also undergo the same process as for the content item/files to configure an IP datagram.

The IP datagrams for the NRT service are contained in at least one RS frame belonging to an ensemble (or referred to as a subnet) when they are transmitted. An IP datagram of the OMA BCAST service guide may also be transmitted in the RS frame. In addition, similar to the mobile service, access information for accessing the NRT service is signaled to the SMT. That is, the SMT provides RT service or NRT service and access information of the components (or content items) contained in each service.

Accordingly, if the service contained in the mobile broadcast is the NRT service, signaling information including the access information of the FLUTE session, which carries content items/files configuring the NRT service, may be extracted from the SMT. In addition, detailed information on content items configuring the NRT service may be extracted from the OMA BCAST service guide (SG) information.

At this time, the SMT contains one NRT service descriptor and one or more capabilities descriptor for each NRT service in the service level.

The NRT service descriptor indicates whether an NRT service exists, identifies the consumption model of the NRT service, and provides other optional information about the NRT service. That is, the NRT service descriptor describes information items indicating that the service described in the service level of the SMT is an NRT service.

The capabilities descriptor provides a list of capabilities used for the NRT service or a content item (e.g., download protocol, FEC algorithm, wrapper/archive formats, compression algorithm, and media type). In addition, a nonessential protocol may be listed. That is, the capabilities descriptor describes the capabilities of the files configuring the NRT service.

Meanwhile, for the broadcast receiver to process disaster-related additional information received in NRT and provide the processed information to the user, information allowing identifying the files received in NRT as disaster-related additional information is needed.

In one embodiment of the present invention, the information for identifying a file as disaster-related additional information is signaled to at least one of the NRT service descriptor and the capabilities descriptor transmitted to the service level of the SMT.

FIG. 49 illustrates the syntax structure of a capabilities descriptor according to one embodiment of the present invention.

In FIG. 49, the descriptor_tag field (8 bits) is a descriptor identifier. An identifier (or a tag value) to identify whether a descriptor is the capabilities descriptor is allocated to this field.

The descriptor_length field (8 bits) indicates the remaining length of this descriptor from the descriptor_length field to the end of the descriptor in unit of byte.

The capability_code_count field (8 bit) indicates the number of values of capability_code. The essential_indicator field and capability_code field are repeated by a value of the capability_code_count field.

The essential_indicator field (1 bit) indicates whether supporting the capability indicated by capability_code is essential for meaningful existence of the NRT service or content item.

The capability_code field (7 bits) indicates a specific capability. If the value of the capability_code field is greater than 0x6F, a format_identifier field indicating an format identifier exists.

The capability_string_count field (8 bits) indicates the number of values of the capability_string. The essential_indicator field, capability_category_code field, capability_string_length field, and capability_string( ) field are repeated by the value of the capability_string_count field.

The essential_indicator field (1 bit) indicates whether supporting the capability indicated by capability_string is essential for meaningful existence of the NRT service or content item.

The capability_category_code field (7 bits) indicates the capability category of a subsequent string value.

The capability_string_length field (8 bits) indicates the length of a subsequent capability_string( ) field.

The capability_string( ) field is a string (i.e, a character string) including the capability.

In one embodiment, the capability_string( ) field, which is capable of classifying files, is used to indicate that a file is related to disaster-related additional information.

That is, by allocating a new string value (e.g., x-application/eas) to the value of the capability_string( ) field, the received files with the “x-application/eas” capability is identified as containing disaster-related additional information.

FIG. 50 illustrates the syntax structure of an NRT service descriptor according to one embodiment of the present invention.

In FIG. 50, the descriptor_tag field (8 bits) is a descriptor identifier. An identifier (or a tag value) to identify whether a descriptor is the NRT service descriptor is allocated to this field.

The descriptor_length field (8 bits) indicates the remaining length of this descriptor from the descriptor_length field to the end of the descriptor in unit of byte.

The consumption_model field (6 bits) signals an intended consumption model for an NRT service associated with the descriptor.

The auto-update field (1 bit) indicates whether to provide an option for automatic updating of the NRT service to the user.

The storage_reservation_present field (1 bit) indicates existence of the storage_reservation field.

The default_content_size_present field (1 bit) indicates existence of the default_content_size field.

The storage_reservation field (24 bit) indicates the minimum storage capacity of the receiver required to store a content item transmitted through the NRT service.

The default_content_size field (40 bit) indicates a default size for the content item.

In one embodiment of the present invention, the consumption model field indicating a description of a scheme in which an NRT service is provided is used to indicate that the NRT service is related to the disaster-related additional information.

That is, a currently reserved value is allocated to the consumption model field, and the files including a NRT service having this value are identified as containing the disaster-related additional information.

FIG. 51 illustrates meanings of the values allocated to the consumption model field. FIG. 51 illustrates an example of allocating 0x04 to the consumption model field in the case that the NRT service is related to the disaster-related additional information.

As described above, by signaling, to NRT service descriptor and/or capabilities descriptor among the descriptors transmitted in the service level of the SMT, the information for identifying whether the files included in the NRT service contains disaster-related additional information broadcast, the disaster-related additional information may be efficiently provided using NRT.

According to one embodiment, the transmitter side may describe the information delivering the ESG corresponding to the NRT service in the GAT, and the broadcast receiver may combine this information and the SMT and download the ESG. The GAT includes information about a provider sending the ESG. At this time, separately sending the ESG information associated with the EAS is more effective for quick transmission of the disaster information. In this case, to distinguish the ESG from an ESG for the existing SG data, the provider name may be allowed to represent the EAS.

FIG. 52 is a flowchart illustrating a method of the broadcast receiver receiving and displaying an emergency alert message containing disaster information and disaster-related additional information according to one embodiment of the present invention.

In FIG. 52, the emergency alert message containing disaster information may be carried in the EAS message descriptor of FIG. 43 or 44 and received, and the disaster-related additional information may be received in the form of a file in NRT. The information identifying whether the file is the disaster-related additional information may be received by being signaled to the capabilities descriptor of FIG. 49 or the NRT service descriptor of FIG. 50. Herein, the EAS message descriptor may be one of the ensemble level descriptor and service level descriptor of the SMT, and each of the capabilities descriptor and NRT service descriptor is one of the service level descriptors of the SMT.

That is, the mobile broadcast is tuned by a tuner of the broadcast receiver (S651), and then a service signaling channel included in the tuned mobile broadcast is acquired (S652). Herein, the service signaling channel may be encapsulated in the IP datagrams having a well-known IP destination address and a well-known destination UDP port number. In other words, all the IP datagrams (i.e., UDP/IP packets) transmitted through the service signaling channel have the same well-known target IP address and the same well-known target UDP port number. For example, when the SMT, RRT, and GAT are assumed to be transmitted through the service signaling channel, all UDP/IP packets transmitting the SMT, RRT, and GAT have the same target IP address and the same target UDP port number. In addition, the target IP address and target UDP port number are well-known values, namely, values known to the receiving system according to agreement by the transmitting/receiving system. Accordingly, signaling tables contained in the service signaling channel may be distinguished from each other by a table identifier. The table identifier may be table_id present in a signaling table or the heater of a signaling table session. If necessary, table_id_extension may be further referenced to distinguish the tables from each other.

Information of the signaling tables distinguished by the table1_id field and/or table_id_extension field is stored in the storage unit of the broadcast receiver (S653). In addition, whether the EAS message descriptor exists in the SMT is confirmed (S654). If the EAS message descriptor exists, the emergency alert message received through the EAS message descriptor is processed and disaster information is displayed in the form of a text on a portion of the screen, as shown in FIG. 47 (S655).

In addition, whether the capabilities descriptor or NRT service descriptor exists in the SMT and whether an indication indicating that a file included in the NRT service is the EAS, i.e., disaster-related additional information is signaled to at least one of the capabilities descriptor and the NRT service descriptor are confirmed (S656).

When it is confirmed in step S656 that an indication indicating the disaster-related additional information is signaled, the NRT service is downloaded (S657). Then, whether the expiration time of the files contained in the downloaded NRT service has passed (S658). If it is confirmed that the expiration time has not passed, disaster-related additional information included in at least one file received in NRT is displayed on a portion of the screen, as shown in FIG. 48 (S659). Herein, the disaster-related additional information may be various types of information such as image, video, and text which are related to the disaster information contained in the emergency alert message.

FIG. 53 is a flowchart illustrating a method of the broadcast receiver receiving and displaying an emergency alert message containing disaster information and disaster-related additional information according to another embodiment of the present invention.

In FIG. 53, the emergency alert message containing disaster information may be carried in the EAS message descriptor of FIG. 44, which include the essential_content_linkage field, and received, and the disaster-related additional information may be received in the form of a file in NRT. The information identifying whether the file is the disaster-related additional information may be received by being signaled to the capabilities descriptor of FIG. 49 or the NRT service descriptor of FIG. 50. Herein, the EAS message descriptor may be one of the ensemble level descriptor and service level descriptor of the SMT, and each of the capabilities descriptor and NRT service descriptor is one of the service level descriptors of the SMT.

That is, the mobile broadcast is tuned by a tuner of the broadcast receiver (S661), and then a service signaling channel included in the tuned mobile broadcast is acquired (S662). The details of the service signaling channel are identical to those illustrated with reference to FIG. 52, and thus a description thereof will be omitted.

Information of the signaling tables identified by the table1_id and/or table_id_extension field included in each signaling table of the service signaling channel is stored in the storage unit of the broadcast receiver (S663). In addition, whether the EAS message descriptor exists in the SMT is confirmed (S664). If the EAS message descriptor exists, the emergency alert message received through the EAS message descriptor is processed and disaster information is displayed in the form of a text on a portion of the screen, as shown in FIG. 47 (S665).

In addition, whether an NRT service related to the EAS exists is conformed (S666). Herein, whether an NRT service related to the EAS exists may be conformed using the num_associated_service field of the EAS message descriptor. If one or more NRT service related to the EAS exists, the EAS message descriptor provides an identifier of the NRT service related to the EAS (associated_service_id).

In step S666, when existence of one or more NRT service related to the EAS is confirmed, an NRT service is downloaded using the corresponding NRT service identifier (S667). Then, whether the value of the essential_content_linkage field of the EAS message descriptor is 0 is confirmed (S668). The essential_content_linkage field indicates the value of linkage between a file included in the NRT service and a content item in the ESG. If the value of the essential_content_linkage field is 0, the user interface (UI) displays a list of NRT services for the EAS (S669). If the value is not 0, the UE displays a file having the value of the essential_content_linkage field as the value of content_linkage on the screen (S670).

As described above, an emergency alert message containing actual disaster information (or content) may be transmitted in the form of a CAP message or syntax.

At this time, an emergency alert message in the form of the CAP or an emergency alert message in the form of syntax may be encapsulated in an IP datagram and transmitted.

That is, as shown in FIG. 54, the IP datagram may be in the form of an IP packet configured with a header and a payload, and the header may be configured with an IP header and a UDP header. In addition, the payload includes an emergency alert message in the form of the CAP or an emergency alert message in the form of syntax. The emergency alert message in the form of syntax included in the payload has the form of a table. This table will be referred to as an EAS table. When the emergency alert message in the form of the CAP is transmitted by the payload, the length of the payload may be calculated based on the length of the IP/UDP header.

FIG. 55 is a view illustrating the syntax structure of an emergency alert system descriptor (emergency_alerting_system_descriptor ( )) transmittable by the payload of FIG. 54. The descriptor may be a session, and the EAS table may be configured using at least one descriptor.

In FIG. 55, the descriptor_tag field (8 bits) is a descriptor identifier. An identifier (or a tag value) to identify whether a descriptor is the emergency alert system descriptor is allocated.

The descriptor_length field (8 bits) indicates the remaining length of this descriptor from the descriptor_length field to the end of the descriptor in unit of byte.

The descriptor_number field (4 bits) indicates the number of the current descriptor among the descriptors included in the EAS table.

The last_descriptor_number field (4 bits) indicates the number of the last descriptor among the descriptors included in the EAS table.

The EAS_event_id field (16 bits) indicates an identifier of an EAS event.

The EAS_originator_code field (24 bits) indicates an entity having activated the EAS.

The EAS_event_code_length field (8 bits) indicates the length of the EAS_event_code field.

The EAS_event_code field (variable) indicates an EAS event, i.e., a type of the EAS. For example, a type of the emergency alert such as flood, earthquake and terrorism may be indicated along with the importance of a specific emergency such as large earthquake, medium earthquake, and small earthquake.

The alert_message_time_remaining field (8 bits) indicates the remaining output time, of an emergency alert message.

The event_start_time field (32 bits) indicates the start time of display of the EAS event.

The event_duration field (16 bits) indicates the duration time of display of the EAS event.

The alert_priority field (4 bits) indicates the priority or importance of the EAS event. That is, depending on the value of the alert_priority field, processing of the received emergency alert message is determined. In other words, whether to unconditionally ignore the emergency alert message or ignore the same under certain conditions, or to compulsorily tune the message to a specific broadcast channel is determined.

The EAS_major_channel_number field (8 bits) indicates a major channel number related to the broadcast channel.

The EAS_minor_channel_number field (8 bits) indicates a minor channel number related to the broadcast channel.

The alert_text_length field (16 bits) indicates the total number of bytes of the alert_text( ) field.

The alert_text( ) field (variable) includes disaster information to be displayed in the form of a text.

The location_code_count field (8 bits) counts region definitions following the ‘for loop’ syntax.

The state_code field (8 bits) indicates a state or territory associated with an emergency alert. The field may have value between 0 and 99.

The county_subdivision field (4 bits) may have a value between 0 and 9 which defines the county division (state subdivision).

The county_code field (10 bits) expresses a specific county associated with the emergency alert among other states. The field may have a value between 0 and 999.

According to one embodiment of the present invention, the emergency alert message may be transmitted at the service level or component level. In the case that the emergency alert message is transmitted at the service level, the emergency alert message is considered as one service, which will be referred to as the EAS service for ease of description. In addition, for the broadcast receiver to support the EAS service, signaling of information to identify the EAS service (hereinafter, referred to as EAS service identifying information) is needed.

In one embodiment of the present invention, one of the reserved values of the MH_service_category field in the service loop of the SMT is used for the EAS service identifying information. According to one embodiment, if a service in the service loop of the SMT is an EAS service, 0x04 may be allocated as the value of the MH_service_category field, as shown in FIG. 56. In this case, the broadcast receiver may recognize that signaling information of the service described in the service loop of the SMT is the signaling information of the EAS service. Herein, 0x04 allocated as the value of the MH_service_category field is simply an example, any category value between 0x00 and 0xFF which is not used by existing services may be allocated. To identify the EAS service, the MH_service_id field may be further used.

In the case that the emergency alert message is transmitted by a separate service, transmitting signaling once for each ensemble is sufficient, and therefore this case is advantageous in view of use of a bandwidth.

Meanwhile, in the case that the emergency alert message is transmitted at the component level, the emergency alert message is considered as one component just as a audio component and a video component. This component will be referred to as an EAS component for ease of description. For the broadcast receiver to support the EAS component, signaling of information to identify an EAS component (hereinafter, referred to as EAS component identifying information) is needed.

In one embodiment of the present invention, one of the reserved values of the component_type field in component_descriptor( ), shown in FIG. 38, among the component level descriptors of the SMT is used for the EAS component identifying information. For example, if a component in the component loop of the SMT is the EAS component, 43 is allocated as the value of the component_type field. In this case, the broadcast receiver may recognize that the signaling information of the component described in the component loop of the SMT is the signaling information of the EAS component. Herein, allocation of 43 to the component_type field is simply an example. Any value between 43 and 71 that is not used by the existing components may be allocated.

The component_type field in component_descriptor( ) indicates a value for identifying the encoding format of a component. This identification value may be one of the values allocated for payload_type of the RTP/AVP stream, one of the values predetermined according to agreement by the transmitter/receiver side, or a dynamic value between 96 and 127. For the components configuring media transmitted via the RTP, a value of the component_type field needs to be identical to the value of payload_type in the RTP header of an IP stream which transmits a corresponding component.

In addition, the component_data (component_type) field, which varies depending upon the value of the component_type field, provides encoding parameters and/or other parameters which are necessary for rendering of a corresponding component. That is, the structure of an component_data element is determined by the value of the component_type field.

For example, if the value of the component_type field is 35, the component_data( ) field provides component data for an H.264/AVC video stream.

If the component_type field is 38, the component_data( ) field provides data for FLUTE file delivery.

If the component_type field is 43, the component_data( ) field provides signaling information for an emergency alert message, as shown in FIG. 57.

FIG. 57 illustrates an example of the bit stream syntax structure of component_data( ), which provides signaling information for an emergency alert message. Fields of the component_data( ) are described below.

In FIG. 57, the EAS_event_ID field (16 bits) indicates a unique identifier of an EAS event corresponding to the emergency alert message.

The payload_type field (2 bits) indicates whether an emergency alert message transmitted in the form of an IP datagram is of the CAP type or the syntax type. In this case, the broadcast receiver is allowed to identify, using the payload_type field, whether the received emergency alert message is CAP type data or syntax type data. That is, the broadcast receiver is allowed to identify the data type of the emergency alert message at the component level.

In another embodiment of the present invention, by allocating the payload_type field to the reserved bits in the component level of the SMT, the data type of the emergency alert message may be identified at the component level.

In another embodiment of the present invention, by allocating the payload_type field to the reserved bits in the service level of the SMT, the data type of the emergency alert message may be identified at the service level.

The status field (6 bits) indicates the status of an emergency alert message.

The urgency field (8 bits) indicates the degree of urgency of a disaster contained in the emergency alert message.

The severity field (8 bits) indicates the degree of severity of a disaster contained in the emergency alert message.

The certainty field (8 bits) indicates the degree of certainty of a disaster contained in the emergency alert message.

The event_start_time field (32 bits) indicates the start time of display of a disaster alert contained in the emergency alert message.

The event_duration field (16 bits) indicates the duration time of a disaster alert contained in the emergency alert message.

Meanwhile, in one embodiment, a new table is defined to signal signaling information for an emergency alert message. This table will be referred to as an emergency alert table (EAT) in this embodiment.

An IP datagram including the EAT may be transmitted through a service signaling channel.

In the case that the EAT is transmitted through the service signaling channel, the EAS_ensemble_indicator field included in the FIC chunk payload of FIG. 42 may indicate whether the EAT is transmitted through the service signaling channel of a corresponding ensemble. For example, if the value of the EAS_ensemble_indicator field is 1, it may indicate that the EAT is transmitted through the service signaling channel included in the ensemble. If the value is 0, it may indicate that the EAT is not transmitted.

The EAT may provide access information of an emergency alert message transmitted in the form of an IP datagram. The access information may include an IP address and a UDP port number.

The service signaling channel through which the EAT is transmitted may further include a signaling table (i.e., at least one of the SMT, GAT, RRT, SLT, and CIT) as well as the EAT. At this time, IP datagrams of the service signaling channel may have the same well-known IP address and well-known UDP port number. Accordingly, the EAT included in the service signaling channel is identified by the table identifier. That is, the table identifier may be table_id existing in the header of the corresponding table or corresponding table section. If necessary, table_id_extension may be further referenced.

FIG. 58 illustrates the bit stream syntax structure of an EAT section according to one embodiment of the present invention. While the EAT section is illustrated as being drafted in the form of an MPEG-2 private section, the format of the data in the EAT section may have any form. At this time, whether the EAT is configured with one section or a plurality of sections may be confirmed through the table_id field, section_number field, and last_section_number field in the EAT section. In addition, a corresponding table may be completed by removing IP headers and UDP headers of the P datagrams from the service signaling channel and collecting sections having the same table identifier. For example, when the sections having the table identifier allocated to the EAT, one EAT may be completed.

Hereinafter, the fields transmittable through the EAT section will be described.

The table_id field (8 bits) is a field to indentify the type of the table. Through this field, it may be confirmed that the table is the EAT.

The section_syntax_indicator field (1 bit) is an indicator to define the section form of the EAT. The section format may be, for example, short-form syntax (‘0’) of MPEG.

The private_indicator field (1 bit) indicates whether the EAT follows the private section.

The section_length field (12 bits) indicates the section length of the remaining EAT subsequent to a corresponding field.

The table_id_extension field (16 bits) is table-dependent, and is a logical portion of the table_id field which provides the range of the remaining fields. The table_id_extension field includes a EAT_protocol_version field and a ensemble_id field.

The EAT_protocol_version field (8 bits) indicates a protocol version to allow the EAT that parameters having a different structure over those defined in a current protocol transmit.

The ensemble_id field (8 bits) is an ID value related to the corresponding ensemble, and a value between 0x00 and 0x3F may be allocated thereto. Preferably, the value of this field is drawn from the parade_id of TPC data. In the case that the ensemble is transmitted through a primary RS frame, the most significant bit (MSB) is set to ‘0’, and the remaining 7 bits are used as a value of parade_id of a corresponding parade. In the case that the ensemble is transmitted through a secondary RS frame, the MSB is set to ‘1’, and the remaining 7 bits are used as a value of parade_id of a corresponding parade.

The version_number field (5 bits) indicates the version number of the EAT.

The current_next_indicator field (1 bit) indicates whether the EAT section is currently applicable.

The section_number field (8 bits) indicates the number of a current EAT section.

The last_section_number field (8 bits) indicates the number of the last section configuring the EAT.

The num_MH_services field (8 bits) indicates the number of mobile services in an EAT section.

By performing ‘for’ loop (or referred to as mobile service loop) by the number of mobile services corresponding to the value of the num_MH_services field, signaling information about a plurality of mobile services is provided. That is, signaling information about each of the mobile services is indicated for each of the mobile services included in the EAT section. At this time, field information may be provided for each mobile service as follows.

The MH_service_id field (16 bits) indicates a value that uniquely identifies a mobile service.

The MH_service_status field (2 bits) identifies the status of the mobile service. Herein, the MSB indicates whether the mobile service is active (‘1’) or non-active (‘0’), and the LSB indicates whether the mobile service is hidden (‘1’) or not (‘0’).

The SP_indicator field (1 bit) indicates whether service protection of the mobile service is applied. If the value of the SP_indicator field is 1, the service protection is applied at least one of the components required for the mobile service to provide meaningful presentation mobile service.

The urgency field (8 bits) indicates the degree of urgency of an emergency alert message contained in the mobile service.

The severity field (8 bits) indicates the degree of severity of the emergency alert message contained in the mobile service.

The certainty field (8 bits) indicates the degree of certainty of the emergency alert message contained in the mobile service.

The event_start_time field (32 bits) indicates the start time of display of the emergency alert message contained in the mobile service.

The event_duration field (16 bits) indicates the duration time of display of the emergency alert message contained in the mobile service.

In the case that the IP_version_flag field (1 bit) is set to ‘1’, it indicates that the service_source_IP_address field and service_destination_IP_address field are IPv6 addresses. In the case that the IP_version_flag field (1 bit) is set to ‘0’, it indicates that the service_source_IP_address field and service_destination_IP_address field are IPv4 addresses.

In the case that the service_source_IP_address_flag field (1 bit) is set to ‘1’, it indicates that a value of the source IP address for the service exists.

In the case that the service_destination_IP_address_flag field (1 bit) is set to ‘1’, it indicates that a value of the destination IP address for the service exists.

The IP_payload_type field (2 bit) indicates whether the emergency alert message transmitted in the form of an IP datagram is of the CAP type or the syntax type.

The service_source_IP_address field (32 or 128 bits) needs to be interpreted when the service_source_IP_address_flag field is set to ‘1’, but does not need to be interpreted when the service_source_IP_address_flag field is set to ‘0’. In the case that the service_source_IP_address_flag field is set to ‘1’, and the IP_version_flag field is set to ‘0’, the above field indicates a 32 bit IPv4 address representing the source of the mobile service. In the case that the IP_version_flag field is set to ‘1’, the above field indicates a 32 bit IPv6 address the source of the mobile service.

The service_destination_IP_address field (32 or 128 bits) needs to be interpreted when the service_destination_IP_address_flag field is set to ‘1’, but does not need to be interpreted when the service_destination_IP_address_flag field is set to ‘0’. In the case that the service_destination_IP_address_flag field is set to ‘1’, and the IP_version_flag field is set to ‘0’, the above field indicates a 32 bit destination IPv4 address for the mobile service. In the case that the service_destination_IP_address_flag field is set to ‘1’, and the IP_version_flag field is set to ‘1’, the above field indicates a 64 bit destination IPv6 address for the mobile service.

Meanwhile, if the value of the severity field is 1, i.e., if a disaster is very severe, compulsory tuning information is signaled.

That is, the force_channel_num field (8 bits) indicates the channel number to be compulsorily tuned, and the force_service_id field (16 bits) indicates a service identifier to be compulsorily tuned.

The num_MH_EAS_descriptor field (8 bits) indicates the number of descriptors that provide additional information of the service level.

A number of MH_EAS_descriptor( ) fields corresponding to the value of the num_MH_EAS_descriptor field are included in the service loop to provide additional information about the emergency alert message.

If the emergency alert message is not transmitted in the form of an IP datagram, the emergency alert message may be included in the MH_EAS_descriptor( ) and transmitted. To this end, the EAT may further include information for identifying whether the emergency alert message is transmitted in the form of an IP datagram or included in the EAT and transmitted.

FIG. 59 is a flowchart illustrating a method of the broadcast receiver receiving and displaying an emergency alert message containing disaster information according to one embodiment of the present invention.

In FIG. 59, the emergency alert message containing disaster information may received in the form of an IP datagram, and the signaling information including the access information of the emergency alert message may be signaled to the EAT and received.

That is, the mobile broadcast is tuned by a tuner of the broadcast receiver (S701), and then an IP datagram of a service signaling channel and an IP datagram including the emergency alert message are identified through IP filtering (S702). In one embodiment, the IP address and the UDP port number for accessing the IP datagram of the service signaling channel may be a well-known IP destination address and a well-known destination UDP port number, respectively. In addition, the IP address and the UDP port number for accessing the IP datagram of the emergency alert message may be signaled to the EAT. In another embodiment, the IP address and the UDP port number for accessing the IP datagram of the emergency alert message may be signaled to the SMT.

Information of each signaling table of the service signaling channel identified by the table1_id field and/or table_id_extension fields of the signaling table is stored in the storage unit of the broadcast receiver (S703). In addition, whether the EAT exists in the service signaling channel is confirmed (S704). The confirmation may be performed using the table1_id field and/or table_id_extension field of the EAT. If the EAT exists, the emergency alert message in the form of the IP datagram is processed using the information included in the FAT. That is, using the value of the payload_type field of the EAT, whether the data received with a payload of the IP datagram is a CAP type emergency alert message of a syntax type emergency alert message is confirmed (S705). If the data is a CAP type emergency alert message, a CAP parser (not shown) processes the emergency alert message (S706). If the data is a syntax type emergency alert message, a syntax parser (not shown) processes the emergency alert message (S707). Then, the processed message is displayed in the form of a text on a portion of the screen as shown in FIG. 47 (S708).

In addition, whether the capabilities descriptor or NRT service descriptor exists in the SMT and whether an indication indicating that a file included in the NRT service is the EAS, i.e., disaster-related additional information is signaled to at least one of the capabilities descriptor and the NRT service descriptor are confirmed (S656).

Herein, at least one file including the additional information related to the emergency alert message (i.e., disaster-related additional information) may be received in NRT, and the signaling information for the disaster-related additional information may be signaled in the service level or component level of the SMT. Then, the received file is processed in NRT based on the signaling information of the disaster-related additional information of the SMT, and the disaster-related additional information received through the file is displayed on a portion of the screen. The disaster-related additional information may be various types of information such as image, video, and text which are related to the disaster information contained in the emergency alert message.

FIG. 60 illustrates a block diagram of a receiving system (i.e., broadcast receiver) to receive and process services such as a mobile service, an EAS service, and an NRT service and so on transmitted through mobile broadcast according to an embodiment of the present invention. Referring to FIG. 60, the arrow shown in dotted line indicates a data path, and the arrow shown in slid line indicates a control signal path.

The receiving system of FIG. 60 may include a controller 2100, a tuner 2111, a demodulator 2112, an equalizer 2113, a known sequence detector (or known data detector) 2114, a block decoder 2115, a primary Reed-Solomon (RS) frame decoder 2116, a secondary RS frame decoder 2117, a signaling decoder 2118, and a baseband operation controller 2119. The receiving system according to the present invention may further include an FIC handler 2121, a service manager 2122, a service signaling handler 2123, and a first storage unit 2124. The receiving system according to the present invention may further include a primary RS frame buffer 2131, a secondary RS frame buffer 2132, and a transport packet (IS) handler 2133. The receiving system according to the present invention may further include an Internet Protocol (IP) datagram handler 2141, a descrambler 2142, an User Datagram Protocol (UDP) datagram handler 2143, a Real-time Transport Protocol/Real-time Transport Control Protocol (RTP/RTCP) datagram handler 2144, a Network Time Protocol (NTP) datagram handler 2145, a service protection stream handler 2146, a second storage unit 2147, an Asynchronous Layered Coding/Layered Coding Transport (ALC/LCT) stream handler 2148, an Extensible Mark-up Language (XML) parser 2150, and a Field Device Tool (FDT) handler 2151. The receiving system according to the present invention may further include an Audio/Video (A/V) decoder 2161, a file decoder 2162, a third storage unit 2163, a middle ware (M/W) engine 2164, and a Service Guide (SG) handler 2165. The receiving system according to the present invention may further include an Electronic Program Guide (EPG) manager 2171, an application manager 2172, and an User Interface (UI) manager 2173.

Herein, for simplicity of the description of the present invention, the tuner 2111, the demodulator 2112, the equalizer 2113, the known sequence detector (or known data detector) 2114, the block decoder 2115, the primary RS frame decoder 2116, the secondary RS frame decoder 2117, the signaling decoder 2118, and the baseband operation controller 2119 will be collectively referred to as a baseband processor 2110. The FIC handler 2121, the service manager 2122, the service signaling handler 2123, and the first storage unit 2124 will be collectively referred to as a service multiplexer 2120. The primary RS frame buffer 2131, the secondary RS frame buffer 2132, and the TS handler 2133 will be collectively referred to as an IP adaptation module 2130. The IP datagram handler 2141, the descrambler 2142, the UDP datagram handler 2143, the RTP/RTCP datagram handler 2144, the NTP datagram handler 2145, the service protection stream handler 2146, the second storage unit 2147, the ALC/LCT stream handler 2148, the XML parser 2150, and the FDT handler 2151 will be collectively referred to as a common IP module 2140. The A/V decoder 2161, the file decoder 2162, the third storage unit 2163, the M/W engine 2164, and the SG handler 2165 will be collectively referred to as an application module 2160.

The terms used in FIG. 60 are general terms that are currently being broadly used. However, according to the advent of new technology, terms deemed to be most appropriate by the applicant are also arbitrarily used in the present invention. The definition of such terms will be described clearly and in detail during the description of the corresponding portion of the present invention. Therefore, the terms used in the present invention should be understood by the significance lying within the terms and not merely by the term itself.

The baseband operation controller 2119 configured as shown in FIG. 60 controls the operation of each block included in the baseband processor 2110.

By tuning the receiving system to the frequency of a specific physical channel (or physical transmission channel (PTC)), the tuner 2111 performs a role enabling the receiving system to receive main service data, which correspond to broadcast signals for fixed broadcast receiving systems, and mobile service data, which correspond to broadcast signals for mobile broadcast receiving systems. The mobile service data may include an emergency alert message. The tuner 2111 down-converts the frequency of the tuned specific channel to an intermediate frequency (IF) and outputs the IF to the demodulator 2112 and the known sequence detector 2114. At this point, the tuner 2111 may receive main service data and mobile service data that are real-time data and receive non-real time service data. Herein, the non-real time service data may include additional information (i.e., disaster related-additional information).

The demodulator 2112 performs self-gain control, carrier wave recovery, and timing recovery on the passband digital IF signal being inputted from the tuner 2111, so as to create a baseband signal. Then, the demodulator 2112 outputs the read baseband signal to the equalizer 2113 and the know sequence detector 2114. When performing carrier wave recovery and timing recovery, the demodulator 2112 may use the known data symbol sequence received from the known sequence detector 2114), so as to enhance the demodulating performance.

The equalizer 2113 compensates the channel distortion included in the demodulated signal, thereby outputting the processed signal to the block decoder 2115. The equalizer 2113 may enhance the equalizing performance by using the known data symbol sequence received from the known sequence detector 2114. Also, the equalizer 2113 may receive feedback on the decoding result of the block decoder 2113, thereby enhancing the equalizing performance.

The known sequence detector 2114 detects the position of the known data being inputted by the transmitting system from the input/output data of the demodulator 2112, i.e., data prior to being processed with the demodulation process or data being partially processed with the demodulation process. Then, along with the detected position information, the known sequence detector 2114 outputs the known data sequence generated from the detected position to the demodulator 2112, the equalizer 2113, and the baseband operation controller 2119. Additionally, the known sequence detector 2114 provides to the block decoder 2115 with information enabling the block decoder 2115 to differentiate mobile service data processed with additional encoding by the transmitting system from main service data that are not processed with any additional encoding.

If the data channel-equalized by the equalizer 2113 and inputted to the block decoder 2115 correspond to data processed with both block-encoding of serial concatenated convolution code (SCCC) method and trellis-encoding by the transmitting system (i.e., data within the RS frame, signaling data), the block decoder 2115 may perform trellis-decoding and block-decoding as inverse processes of the transmitting system. On the other hand, if the data channel-equalized by the equalizer 2113 and inputted to the block decoder 2115 correspond to data processed only with trellis-encoding and not block-encoding by the transmitting system (i.e., main service data), the block decoder 2115 may perform only trellis-decoding.

The signaling decoder 2118 performs decoding on signaling data inputted after being channel-equalized by the equalizer 2113. It is assumed that the signaling data (or signaling information) inputted to the signaling decoder 2118 correspond to data processed with both block-encoding and trellis-encoding by the transmitting system. According to an embodiment of the present invention, the signaling data includes TPC (Transmission Parameter Channel) data and FIC (Fast Information Channel). For example, the signaling decoder 2118 performs regressive turbo decoding using a parallel concatenated convolution code (PCCC) method on the data of the signaling information region among the inputted data. Then, the signaling decoder 2118 separates the FIC data and TPC data from the turbo-decoded signaling data. Also, the signaling decoder 2118 performs RS-decoding on the separated TPC data as an inverse process of the transmitting system, thereby outputting the RS-decoded TPC data to the baseband operation controller 2119. Furthermore, the signaling decoder 2118 performs deinterleaving on the separated FIC data in subframe units and then performs RS-decoding on the deinterleaved FIC data as an inverse process of the transmitting system, thereby outputting the RS-decoded data to the FIC handler 2121. The transmission unit of the FIC data being deinterleaved and RS-decoded by the signaling decoder 2118 and being outputted to the FIC handler 2121 corresponds to FIC segments.

The FIC handler 2121 receives FIC data from the signaling decoder 2118, so as to extract signaling information for service acquisition (i.e., mapping information between an ensemble and a mobile service). In order to do so, the FIC handler 2121 may include an FIC segment buffer, an FIC segment parser, and an FIC chunk parser.

The FIC segment buffer buffers FIC segment groups being inputted in M/H frame units from the signaling decoder 2118, thereby outputting the buffered FIC segments to the FIC segment parser. Thereafter, the FIC segment parser extracts the header of each FIC segment stored in the FIC segment buffer so as to analyze the extracted headers. Then, based upon the analyzed result, the FIC segment parser outputs the payload of the respective FIC segments to the FIC chunk parser. The FIC chunk parser uses the analyzed result outputted from the FIC segment parser so as to recover the FIC chunk data structure from the FIC segment payloads, thereby analyzing the received FIC chunk data structure. Subsequently, the FIC chunk parser extracts the signaling information for service acquisition. The signaling information acquired from the FIC chunk parser is outputted to the service manager 2122. According to an embodiment of the present invention, the FIC segment header includes a wake_up_indicator field. Reference may be made to FIG. 39 or FIG. 40 for the detailed description of the wake_up_indicator field. Furthermore, according to an embodiment of the present invention, the FIC chunk payload includes an EAS_ensemble_indicator field. Reference may be made to FIG. 42 for the detailed description of the EAS_ensemble_indicator field.

Meanwhile, the service signaling handler 2123 is configured of a service signaling buffer and a service signaling parser, and the service signaling handler 2123 buffers table sections, for example, SMT sections and EAT sections of a service signaling channel being transmitted from the UDP datagram handler 2143, thereby analyzing and processing the buffered table sections. The SMT information and the EAT information processed by the service signaling handler 2123 is also outputted to the service manager 2122.

According to an embodiment of the present invention, the service signaling channel transmitting the SMT section and/or the EAT section is included in a corresponding RS frame in a UDP/IP packet form having well-known destination IP address and well-known destination UDP port number and is received. Accordingly, the receiving system may parse the SMT section and descriptors of the SMT section without requiring extra information. This is identically applied to the EAT.

Furthermore, the SMT section provides signaling information (including IP access information) about all services within the ensemble that the SMT section is included. Therefore, the receiving system may access an IP stream component belonging to a desired service by using information parsed from the SMT section, thereby providing the service to the user. In addition, the receiving system may access the emergency alert message by using EAS-related signaling information included in the EAT, thereby providing the disaster information to the user.

If the service is an NRT service, access information of an FLUTE session that transmits content/files configuring of the NRT service may be extracted from the SMT.

The information parsed from the SMT is collected by the service manager 2122 and is stored in the first storage unit 2124. The service manager 2122 stores the information extracted from the SMT as a service map and a guide data form in the first storage unit 2124.

That is, service manager 2122 uses the signaling information collected (or gathered) from the FIC handler 2121 and the service signaling handler 2123 so as to configure a service map, and the service manager 2122 uses the service guide (SG) collected from the service guide (SG) handler 2165 so as to configure a program guide. Then, the service manager 2122 refers to the configured service map and program guide to control the baseband operation controller 2119 so that the user can receive the mobile service he (or she) wishes. Also, depending upon the user's input, the service manager 2122 may perform controlling operations enabling the program guide to be displayed on at least one portion of the display screen.

The first storage unit 2124 stores the service map and service guide drawn up by the service manager 2122. Also, based upon the requests from the service manager 2122 and the EPG manager 2171, the required data are extracted from the first storage unit 2124, which are then transferred to the service manager 2122 and/or the EPG manager 2171.

The baseband operation controller 2119 receives the known data place information and TPC data, thereby transferring M/H frame time information, information indicating whether or not a data group exists in a selected parade, place information of known data within a corresponding data group, power control information, and so on to each block within the baseband processor 2110.

Meanwhile, according to the present invention, the transmitting system uses RS frames by encoding units. Herein, the RS frame may be divided into a primary RS frame and a secondary RS frame. However, according to the embodiment of the present invention, the primary RS frame and the secondary RS frame will be divided based upon the level of importance of the corresponding data.

The primary RS frame decoder 2116 receives the data outputted from the block decoder 2115. At this point, according to the embodiment of the present invention, the primary RS frame decoder 2116 receives the mobile service data or NRT service data that have been Reed-Solomon (RS)-encoded and/or cyclic redundancy check (CRC)-encoded from the block decoder 2115. The primary RS frame decoder 2116 receives the SMT section data or the OMA BCAST SG data that have been Reed-Solomon (RS)-encoded and/or cyclic redundancy check (CRC)-encoded from the block decoder 2115.

In other words, the primary RS frame decoder 2116 receives at least one of the mobile service data, the NRT service data, the SMT section data and the OMA BCAST SG data but no main service data. The primary RS frame decoder 2116 performs inverse processes of the RS frame encoder (not shown) included in the digital broadcast transmitting system, thereby correcting errors existing within the primary RS frame. More specifically, the primary RS frame decoder 2116 forms a primary RS frame by grouping a plurality of data groups and, then, correct errors in primary RS frame units. In other words, the primary RS frame decoder 2116 decodes primary RS frames, which are being transmitted for actual broadcast services. The primary RS frame decoded by the primary RS frame decoder 2116 is output to the primary RS frame buffer 2131. The primary RS frame buffer 2131 buffers the primary RS frame, and then configures an M/H TP in each row unit. The M/H TPs of the primary RS frame outputs to the TP handler 2133.

Additionally, the secondary RS frame decoder 2117 receives the data outputted from the block decoder 2115. At this point, according to the embodiment of the present invention, the secondary RS frame decoder 2117 receives the mobile service data or the NRT service data that have been RS-encoded and/or CRC-encoded from the block decoder 2115. The secondary RS frame decoder 2117 receives the SMT section data or the OMA BCAST SG data that have been Reed-Solomon (RS)-encoded and/or cyclic redundancy check (CRC)-encoded from the block decoder 2115.

That is, the secondary RS frame decoder 2117 receives at least one of the mobile service data, the NRT service data, the SMT section data and the OMA BCAST SG data but no main service data. The secondary RS frame decoder 2117 performs inverse processes of the RS frame encoder (not shown) included in the digital broadcast transmitting system, thereby correcting errors existing within the secondary RS frame. More specifically, the secondary RS frame decoder 2117 forms a secondary RS frame by grouping a plurality of data groups and, then, correct errors in secondary RS frame units. In other words, the secondary RS frame decoder 2117 decodes secondary RS frames, which are being transmitted for mobile audio service data, mobile video service data, guide data, and so on. The secondary RS frame decoded by the secondary RS frame decoder 2117 is output to the secondary RS frame buffer 2132. The secondary RS frame buffer 2132 buffers the secondary RS frame, and then configures an M/H TP in each row unit. The M/H TPs of the secondary RS frame outputs to the TP handler 2133.

The TP handler 2133 consists of a TP buffer and a TP parser. The TP handler 2133 buffers the M/H TPs inputted from the primary RS frame buffer 2131 and the secondary RS frame buffer 2132, and then extracts and analyzes each header of the buffered M/Hi TPs, thereby recovering IP datagram from each payload of the corresponding M/H TPs. The recovered IP datagram is outputted to the IP datagram handler 2141.

The IP datagram handler 2141 consists of an IP datagram buffer and an IP datagram parser. The IP datagram handler 2141 buffers the IP datagram delivered from the TP handler 2133, and then extracts and analyzes a header of the buffered IP datagram, thereby recovering UDP datagram from a payload of the corresponding IP datagram. The recovered UDP datagram is outputted to the UDP datagram handler 2143.

If the UDP datagram is scrambled, the scrambled UDP datagram is descrambled by the descrambler 2142, and the descrambled UDP datagram is outputted to the UDP datagram handler 2143. For example, when the UDP datagram among the received IP datagram is scrambled, the descrambler 2142 descrambles the UDP datagram by inputting an encryption key and so on from the service protection stream handler 2146, and outputs the descrambled UDP datagram to the UDP datagram handler 2143.

The UDP datagram handler 2143 consists of an UDP datagram buffer and an UDP datagram parser. The UDP datagram handler 2143 buffers the UDP datagram delivered from the IP datagram handler 2141 or the descrambler 2142, and then extracts and analyzes a header of the buffered UDP datagram, thereby recovering data transmitted through a payload of the corresponding UDP datagram. If the recovered data is an RTP/RTCP datagram, the recovered data is outputted to the RTP/RTCP datagram handler 2144. If the recovered data is also an NTP datagram, the recovered data is outputted to the NTP handler 2145. Furthermore, if the recovered data is a service protection stream, the recovered data is outputted to the service protection stream handler 2146. And, if the recovered data is an ALC/LCT stream, the recovered data is outputted to the ALC/LCT steam handler 2148. Furthermore, if the recovered data are the SMT section data or the EAT section data, the recovered data are outputted to the service signaling section handler 2123.

At this point, since the service signaling channel transmitting the SMT section or the EAT section is an IP datagram having well-known destination IP address and well-known destination UDP port number, the IP datagram handler 2141 and the UDP datagram handler 2143 may output the data included in the SMT section and/or the EAT section without requiring extra information to the service signaling section handler 2123.

The RTP/RTCP datagram handler 2144 consists of an RTP/RTCP datagram buffer and an RTP/RTCP datagram parser. The RTP/RTCP datagram handler 2144 buffers the data of RTP/RTCP structure outputted from the UDP datagram handler 2143, and then extracts A/V stream from the buffered data, thereby outputting the extracted A/V stream to the A/V decoder 2161. The A/V decoder 2161 decodes the audio and video streams outputted from the RTP/RTCP datagram handler 2144 using audio and video decoding algorithms, respectively. The decoded audio and video data is outputted to the presentation manager 2170. Herein, at least one of an AC-3 decoding algorithm, an MPEG 2 audio decoding algorithm, an MPEG 4 audio decoding algorithm, an AAC decoding algorithm, an AAC+ decoding algorithm, an HE AAC decoding algorithm, an AAC SBR decoding algorithm, an MPEG surround decoding algorithm, and a BSAC decoding algorithm can be used as the audio decoding algorithm and at least one of an MPEG 2 video decoding algorithm, an MPEG 4 video decoding algorithm, an H.264 decoding algorithm, an SVC decoding algorithm, and a VC-1 decoding algorithm can be used as the audio decoding algorithm.

The NTP datagram handler 2145 consists of an NTP datagram buffer and an NTP datagram parser. The NTP datagram handler 2145 buffers data having an NTP structure, the data being outputted from the UDP datagram handler 2143. Then, the NTP datagram handler 2145 extracts an NTP stream from the buffered data. Thereafter, the extracted NTP stream is outputted to the A/V decoder 2161 so as to be decoded.

The service protection stream handler 2146 may further include a service protection stream buffer. Herein, the service protection stream handler 2146 buffers data designated (or required) for service protection, the data being outputted from the UDP datagram handler 2143. Subsequently, the service protection stream handler 2146 extracts information required for descrambling from the extracted data. The information required for descrambling includes a key value, such as SKTM and LKTM. The information for descrambling is stored in the second storage unit 2147, and, when required, the information for descrambling is outputted to the descrambler 2142.

The ALC/LCT stream handler 2148 consists of an ALC/LCT stream buffer and an ALC/LCT stream parser. And, the ALC/LCT stream handler 2148 buffers data having an ALC/LCT structure, the data being outputted from the UDP datagram handler 2143. Then, the ALC/LCT stream handler 2148 analyzes a header and a header expansion of an ALC/LCT session from the buffered data. Based upon the analysis result of the header and header expansion of the ALC/LCT session, when the data being transmitted to the ALC/LCT session correspond to an XML structure, the corresponding data are outputted to an XML parser 2150. Alternatively, when the data being transmitted to the ALC/LCT session correspond to a file structure, the corresponding data are outputted to a file decoder 2162.

At this point, when the data that are being transmitted to the ALC/LCT session are compressed, the compressed data are decompressed by a decompressor 2149, thereby being outputted to the XML parser 2150 or the file decoder 2162.

The XML parser 2150 analyses the XML data being transmitted through the ALC/LCT session. Then, when the analyzed data correspond to data designated to a file-based service, the XML parser 2150 outputs the corresponding data to the FDT handler 2151. On the other hand, if the analyzed data correspond to data designated to a service guide, the XML parser 2150 outputs the corresponding data to the SG handler 2165.

The FDT handler 2151 analyzes and processes a file description table of a FLUTE protocol, which is transmitted in an XML structure through the ALC/LCT session. The FDT handler 2151 is controlled by the service manager 2122 when the received file is the file for the NRT service. The file may include the disaster-related additional information.

The SG handler 2165 collects and analyzes the data designated for a service guide, the data being transmitted in an XML structure, thereby outputting the analyzed data to the service manager 2122.

The file decoder 2162 decodes the data having a file structure and being transmitted through the ALC/LCT session, thereby outputting the decoded data to the middleware engine 2164 or storing the decoded data in a third storage unit 2163. According to an embodiment of the present invention, the data of a file structure that are decoded by the file decoder 2162 include the NRT service data.

Herein, the middleware engine 2164 translates the file structure data (i.e., the application) like the NRT service and executes the translated application. Thereafter, the application may be outputted to an output device, such as a display screen or speakers, through the application presentation manager 2170. According to an embodiment of the present invention, the middleware engine 2164 corresponds to a JAVA-based middleware engine.

Based upon a user-input, the EPG manager 2171 receives EPG data either through the service manager 2122 or through the SG handler 2165, so as to convert the received EPG data to a display format, thereby outputting the converted data to the presentation manager 2170.

The application manager 2172 performs overall management associated with the processing of application data (for example, NRT service data), which are being transmitted in object formats, file formats, and so on.

Furthermore, based upon a user-command inputted through the UI manager 2173, the operation controller 2100 controls at least one of the service manager 2122, the EPG manager 2171, the application manager 2172, and the presentation manager 2170, so as to enable the user-requested function to be executed.

The UI manager 2173 transfers the user-input to the operation controller 2100 through the UI.

Finally, the presentation manager 2170 provides at least one of the audio and video data being outputted from the A/V decoder 2161 and the EPG data being outputted from the EPG manager 2171 to the user through the speaker and/or display screen.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the inventions. Thus, it is intended that the present invention covers the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.

As described above, the present invention is described with respect to the best mode for carrying out the present invention.

As described above, the present invention may be fully (or entirely) or partially applied to broadcast and communication fields an embodiment of a transmitting system, a receiving system and method of processing a broadcast signal according to the present invention. 

What is claimed is:
 1. A method of receiving an emergency alert message by a broadcast terminal in a sleep mode, the method comprising: monitoring, by the broadcast terminal, fast information channel (FIC) wake-up indicator in an FIC segment to determine if the broadcast terminal should be switched to an active mode to receive the emergency alert message; getting an FIC-Chunk payload responsive to the FIC wake-up indicator in the FIC segment, the FIC-Chunk payload including an emergency alert data package indicator; receiving an alert data indicated by a data package identification (ID) included in the FIC-Chunk payload, the emergency alert data package indicator indicating an emergency alert table describing the emergency alert message is carried in the data; and parsing the emergency alert message based on the emergency alert table.
 2. The method of claim 1, wherein the monitoring step further comprises: monitoring a version value of FIC data in transmission parameter; and gathering complete FIC segment data.
 3. The method of claim 2, wherein the gathering step includes receiving at least one Reed-Solomon (RS) frame.
 4. The method of claim 2, wherein the FIC segment further includes a major protocol version value.
 5. The method of claim 2, further comprising: switching the broadcast terminal to the active mode to receive an emergency alert message responsive to an indication in the value of the FIC wake-up indicator that switching to the active mode is compulsory; and remaining in the sleep mode responsive to no change in the version value of the FIC data or indication in the value of the FIC wake-up indicator that switching to the active mode is not compulsory.
 6. The method of claim 4, wherein the FIC segment further includes a minor protocol version value to indicate a backward-compatible level of change.
 7. The method of claim 1, wherein the receiving step receives the emergency alert message in a Common Alerting Protocol format.
 8. The method of claim 7, wherein the emergency alert message is compressed when received and decompressed for display.
 9. The method of claim 1, wherein the data package ID is an identifier to identify a data package including at least a service map table (SMT) and an emergency alert table (EAT).
 10. The method of claim 9, wherein the receiving step does not require reference to the SMT.
 11. The method of claim 1, wherein the emergency alert message is received via a service signaling channel.
 12. A broadcast terminal configured to wake up from a sleep mode to receive an emergency alert message, the broadcast terminal comprising: a baseband processor configured to receive a broadcast signal; a fast information channel (FIC) handler configured to: receive, from the baseband processor, decoded signals decoded from the broadcast signal, monitor fast information channel (FIC) wake-up indicator in an FIC segment among the decoded signals to determine if the broadcast terminal should be switched to an active mode to receive the emergency alert message, getting an FIC-Chunk payload responsive to the FIC wake-up indicator in the FIC segment, the FIC-Chunk payload including an emergency alert data package indicator, and set an data package identification (ID) included in the FIC-Chunk payload for receiving an data package indicated by the data package ID, the emergency alert data package indicator indicating an emergency alert table is carried in the data package; and a controller configured to receive signals from the FIC handler.
 13. The broadcast terminal of claim 12, wherein the FIC handler is further configured to: monitor a version value of FIC data in transmission parameter, and gather complete FIC segment data.
 14. The broadcast terminal of claim 13, wherein the FIC handler is further configured to receive at least one Reed-Solomon (RS) frame to complete gathering.
 15. The broadcast terminal of claim 13, wherein the FIC handler is further configured to monitor a major protocol version value.
 16. The broadcast terminal of claim 13, wherein the controller is further configured to: switch the broadcast terminal to the active mode to receive an emergency alert message responsive to an indication in the value of the FIC wake-up indicator that switching to the active mode is compulsory, and remain in the sleep mode responsive to no change in the major protocol version value of the FIC data or indication in the value of the FIC wake-up indicator that switching to the active mode is not compulsory.
 17. The broadcast terminal of claim 12, wherein the baseband processor is further configured to receive the emergency alert message in a Common Alerting Protocol format in the broadcast signal, and wherein the emergency alert message is compressed when received and decompressed for display.
 18. The broadcast terminal of claim 12, wherein the data package D is an identifier to identify a data package including at least a service map table (SMT) and an emergency alert table (EAT).
 19. The broadcast terminal of claim 18, wherein the baseband processor is further configured to receive the emergency alert message without reference to the SMT.
 20. The broadcast terminal of claim 12, wherein the baseband processor is further configured to receive the emergency alert message via a service signaling channel. 